From: Mike McCormack <mike@codeweavers.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Martin Langhoff <martin@catalyst.net.nz>
Subject: Re: pushing patches to an imap folder
Date: Wed, 16 Nov 2005 10:53:13 +0900 [thread overview]
Message-ID: <437A9109.6010101@codeweavers.com> (raw)
In-Reply-To: <7vzmo5ka20.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Wow. How is the acceptance by wine community? Favorable, I
> hope.
wine.git hasn't been announced on any of the wine mailing lists yet. As
long as we don't get rid of CVS entirely, I don't think there'll be too
many complaints. Hopefully when it's announced, we'll have a few GIT
users who can tell people why it's good to use.
> git-cvsexportcommit? I haven't had a chance to use it myself,
> although I have to interoperate with CVS in some projects.
> Martin, do you want to do a plug (or brag) here?
git-cvsexportcommit looks nice. I guess Alexandre is using something
like that now. I was thinking more ambitiously... something like a
git-cvsd. That would be a pretty awesome migration tool :)
> It is handy, especially for simple things like rebasing topic
> branches, when the things are of managable size without using
> quilt or StGIT. Do you manage binary files?
No, there's no binary files in the Wine CVS (or symlinks ;).
> Yes, I saw that value there. Maybe adding hooks to format-patch
> so that it can do form-letter-ish things you had to add there
> without patching might help? I dunno.
I'll have a go at integrating my code with format-patch. Hooks for a
template would be helpful.
Mike
next prev parent reply other threads:[~2005-11-16 1:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 8:20 pushing patches to an imap folder Mike McCormack
2005-11-15 9:12 ` Junio C Hamano
2005-11-15 10:35 ` Mike McCormack
2005-11-15 11:36 ` Johannes Schindelin
2005-11-16 23:49 ` Matthias Urlichs
2005-11-15 19:03 ` Junio C Hamano
2005-11-16 1:53 ` Mike McCormack [this message]
2005-11-16 3:15 ` Junio C Hamano
2005-11-16 3:18 ` Mike McCormack
2005-11-16 3:45 ` Martin Langhoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=437A9109.6010101@codeweavers.com \
--to=mike@codeweavers.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=martin@catalyst.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.