Lines Matching full:work

6 Sooner or later, the time comes when your work is ready to be presented to
23 work being done is complex, though, there is a lot to be gained by getting
24 feedback from the community before the work is complete.  So you should
25 consider posting in-progress work, or even making a git tree available so
26 that interested developers can catch up with your work at any time.
29 good idea to say so in the posting itself.  Also mention any major work
32 with the idea that they can help you drive the work in the right direction.
53  - Be sure that you have the right to post the code.  If this work was done
54    for an employer, the employer likely has a right to the work and must be
64 The preparation of patches for posting can be a surprising amount of work,
77 against these other trees can require a significant amount of work
111    users who are engaging in the noble work of tracking down problems.
128 which takes quite a bit of time and thought after the "real work" has been
135 So now you have a perfect series of patches for posting, but the work is
221    attributed by the From: tag) when multiple people work on a single patch.
231    it to work.
239    people who test our code and let us know when things do not work
262    helpful hints on making specific mail clients work for sending patches.