From: David Brown <git@davidb.org>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Help breaking up a large merge.
Date: Thu, 18 Sep 2008 10:47:05 -0700 [thread overview]
Message-ID: <20080918174705.GA8055@linode.davidb.org> (raw)
In-Reply-To: <32541b130809181040p4785f877s7502c578e46745d8@mail.gmail.com>
On Thu, Sep 18, 2008 at 01:40:55PM -0400, Avery Pennarun wrote:
>1) Generate a giant patch file using 'git diff X..A'. Call the patch P.
>
>2) Using an editor, divide up the patch by files/subdirs based on how
>you want to subdivide the work. Or alternatively, do that with 'git
>diff' itself, but beware of accidentally forgetting to ask for some
>files if you do it that way. Call these n individual patches P1..Pn.
The is fairly close to the approach I've been taking, but somehow I
didn't think of using the output of diff itself and hacking that up.
I like this because it makes it easier to not forget some files.
It is likely there will be makefiles to cleanup and such, but
otherwise I like this idea.
Thanks,
David
prev parent reply other threads:[~2008-09-18 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 15:21 Help breaking up a large merge David Brown
2008-09-18 15:55 ` Santi Béjar
2008-09-18 16:25 ` David Brown
2008-09-18 16:41 ` Johannes Sixt
2008-09-18 17:40 ` Avery Pennarun
2008-09-18 17:47 ` David Brown [this message]
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=20080918174705.GA8055@linode.davidb.org \
--to=git@davidb.org \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
/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.