Re: A stupid procedural question re CVS

[Federico Mena <federico nuclecu unam mx>]

>   > >    1) fix the bug and submit diffs (but to whom?) or
>   > >    2) fix the bug and commit (but that requires write access), or
>   > >    3) fetch the current version and hope it's fixed there?
>  
>  What if my update crosses someone's commit?  Seems like one iteration
>  of #3 is appropriate before embarking on #1.

Well, of course... if you are trying to fix a bug, most of the time
you are expected to work from the latest version of the source :-)

>  Aha!  I just failed to mention the module, so it gave me all of them (gulp).
>  
>  Maybe I ought to be sending questions of this sort to the
>  gnome-cvs-operations-for-clueless-dweebs-who-have-not-read-the-man-page@gnome.org
>  mailing list?

No problem.  I'd suggest looking at the info documentation for cvs;
it's pretty good and nicely laid out in a tutorial fashion.

  Quartic