On Thu, 2009-01-15 at 16:39 -0500, Eric M. Ludlam wrote:
> >>> Jan Moringen <jan.moringen@...> seems to think that:
> [ ... ]
> >> If you plan on having several patches over time, I can add you as
> >> a developer so you can check your changes into CVS directly.
> >I do plan to submit more patches. It would be nice to directly use CVS
> >instead of preparing, testing and submitting patches. But how would the
> >changes get reviewed then? Or are there CVS branches that I am not aware
> [ ... ]
> Branches are one way, and using vc-diff (C-x v =) will generate
> patches easily enough. If you have little stuff, sharing small diffs
> via email is usually enough for me to get the gist of it. If you've
> got big stuff, you can create your own branches you can use instead.
> I'm not too picky.
Then for now I will do the following: for everything that changes
complex or well established parts, I will send patches, while I will use
CVS to work on new things I might add.
> I put my CVS comments in as change-log style entries. I have a script
> that extracts the CVS comments into a ChangeLog, before creating a
> distribution. You can look at existing comments for how it's done.
I did the in most of my recent projects.
> Hopefully, I can add you as a developer tonight.