From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: git@vger.kernel.org
Subject: Re: splitting large patch files into smaller ones
Date: Thu, 23 Aug 2007 10:43:41 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708231042120.20400@racer.site> (raw)
In-Reply-To: <200708221929.l7MJTgiL012452@agora.fsl.cs.sunysb.edu>
Hi,
On Wed, 22 Aug 2007, Erez Zadok wrote:
> I was looking around for a tool that would allow me to split a large
> patch file into individual snippets and couldn't find one. So I wrote
> one in perl. It takes a patch file and creates individual small files,
> one for each combination of a filename listed in the patch, and a patch
> snippet (starting with an '@@' line). Each '@@' snippet gets an index
> number and a new filename, prefixed with the appropriate header ("diff
> ...", ---, and +++ lines) so it's a valid patch file on its own.
You can do that with "git add -i" and with "git gui" AFAIK. I even
started some code to split hunks in "git gui", but it was pointed out that
that code was not complete, and I did not have time to finish it.
Ciao,
Dscho
prev parent reply other threads:[~2007-08-23 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 19:29 splitting large patch files into smaller ones Erez Zadok
2007-08-22 21:54 ` René Scharfe
2007-08-23 9:43 ` Johannes Schindelin [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=Pine.LNX.4.64.0708231042120.20400@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=ezk@cs.sunysb.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).