Re: pushing patches to an imap folder

From: Mike McCormack <mike@codeweavers.com>
Date: Nov 15, 2005, 10:35 UTC
Message-ID: <4379B9F6.5020402@codeweavers.com>
In-Reply-To: <7vd5l2qnq6.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:

> Hmph.  How well does the rest of git help your workflow, working
> with the Wine community?  Especially, how are you keeping track
> of and interoperating with their main CVS repository?

We have a (semi-experimental) wine.git tree, which is updated at the same time as the Wine CVS, by the project maintainer:

http://source.winehq.org/git/wine.git

It will probably be maintained in parallel with the Wine CVS for a while, unless somebody writes a GIT->CVS gateway.

I find git-rebase to be particularly useful. When I used CVS, sending a series of patches was a pain. I'd contemplated using quilt, but never got round to trying it.

Pushing patches from git into a drafts folder means I don't have to manually generate a diff, open a mail, type the mailing list address, attach the patch and write/copy-paste a ChangeLog entry.

> Do you
> have to do anything special when your patches are accepted by
> the upstream and echoed back to you when you 'cvs update' from
> them next time?

"git pull" is usually sufficient.

Mike