I am new to open source so forgive me. How do I know if someone is
working on (or in) the sections that I want to work on? Where I work
we can look into our source management tool and see who is working on
which files. Also, if that person is changing or updating files they
check them out and lock them. In this HUGE open source project how do
we keep from "stepping" on each others toes?
Shane
Jon Griffiths wrote:
>
> On Wednesday 03 January 2001 06:42, Shane Nifong wrote:
> > I am starting to work on the advapi32 functions. I was wondering if I
> > make changes to the stub files that are there how often to I create
> > patches or update using CVS?
> > Should I create patches first?
>
> I normally work in one or more sperate build trees, and update my source tree
> every couple of days. When I'm ready to send a patch , I update and copy out
> the latest cvs, then merge my changes in to that tree, create a patch, test
> it, and submit.
>
> You can send patches whenever you want, I usually wait until I've implemented
> a set of related functionality or I've made one of my test programs happy. If
> you're working on an area no one else is (as I have been), then sending
> patches infrequently isn't a problem since your work won't get confused by
> other peoples updates. If you need to fix something outside of the dll
> directory to make thing work, you should probably send a patch for that
> sonner, because if its not broken, you may be going about it the wrong way
> (and if it is, is should be fixed ASAP for other developers).
>
> For your first patch you might want to send it sooner rather than later, just
> to be sure your approach will be accepted. Once youre confident that you are
> going about it the right way (tm), you can hang back and send your patches
> less frequently.
>
> Cheers,
> Jon
>
> --
> "May their negative actions ripen upon me. And may all my virtues ripen upon
> them."
> "If it could be talked about, everybody would have told their brother."
> [EMAIL PROTECTED] , [EMAIL PROTECTED]
