From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'git mailing list'" <git@vger.kernel.org>
Subject: [RFE/RFC] format-patch/diff via path
Date: Sat, 20 Jan 2018 01:26:02 -0500 [thread overview]
Message-ID: <018601d391b7$8e8686a0$ab9393e0$@nexbridge.com> (raw)
I’m still a bit perplexed by some behaviour seen today, and am looking for a clean way to deal with it that the documentation does not make clear. So, I’m asking in a different way. Suppose a graph of
A---B---C---D---E
\ \ /
\----F—G----/
When trying to perform a format-patch from B to E, I was seeing commits B-A-F-G-E rather than what I wanted B-C-D-E. F and G were younger commits than C and D, which I assume (very likely wrongly) is why diff was giving preferential treatment to that path.
What I am trying to figure out is whether there is a clean way to force format-patch along the B-C-D-E path. If not, would it be worth starting up a small project to make this possible (not knowing exactly where to start), but I would envision something like: git format-patch –via=C B..E
I may be just missing something obvious (new to format-patch operations myself).
Cheers,
Randall
P.S. Bad ideas happen when tests run for a long time 😉
-- Brief whoami:
NonStop developer since approximately NonStop(211288444200000000)
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
next reply other threads:[~2018-01-20 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 6:26 Randall S. Becker [this message]
2018-01-20 7:14 ` [RFE/RFC] format-patch/diff via path Junio C Hamano
2018-01-20 7:41 ` Randall S. Becker
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='018601d391b7$8e8686a0$ab9393e0$@nexbridge.com' \
--to=rsbecker@nexbridge.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.
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).