From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Git Mailing list <git@vger.kernel.org>
Subject: can someone verify operation of "splitpatch" with a massive "git diff"?
Date: Mon, 16 Nov 2020 04:18:24 -0500 (EST) [thread overview]
Message-ID: <fc5cf6bc-aa74-d8-90b-c1789f349b8c@crashcourse.ca> (raw)
someone just handed me a several thousand line layer-wide patch, and
i'd like to pull it apart into bite-sized pieces, and i just noticed
the utility "splitpatch", but when i applied it to the patch, what i
got was *almost* right ... except that the patch snippets had the
trailing "git diff" line from the *following* patch snippet in the
file; the splitting operation clearly retained the trailing line after
the patch, rather than the leading line that actually represented the
snippet.
is there a simple way to do this? i do have the right to go back to
the patch creator and ask him to redo the diff in a different way.
thoughts?
rday
next reply other threads:[~2020-11-16 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 9:18 Robert P. J. Day [this message]
2020-11-17 19:51 ` can someone verify operation of "splitpatch" with a massive "git diff"? René Scharfe
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc5cf6bc-aa74-d8-90b-c1789f349b8c@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).