git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Spencer Baugh <sbaugh@catern.com>
To: git@vger.kernel.org
Subject: New flag (and trailer) for git-quiltimport.sh and git format-patch
Date: Sat, 18 Jul 2015 16:04:55 -0400	[thread overview]
Message-ID: <87h9p1qljs.fsf@earth.i-did-not-set--mail-host-address--so-tickle-me> (raw)


Hi git list,

I think it would be useful if git-quiltimport.sh recognized a flag to
tell it to add a "QuiltFilename:" or "PatchFilename:" trailer to each
imported commit, which would show the filename of the patch that that
commit was imported from.

This would make it much easier (reliably possible, in fact) to match up
imported commits with their original patch; this is something I
frequently want to do, since the original patches might have additional
information associated with them that is not imported into git. (For
example, a comment in the quilt "series" file, or version control
history of the patch if it is kept in version control).

If such a flag and trailer were added, I think another useful addition
could be made to git format-patch: a flag to read the "PatchFilename: "
trailer and create the patch with that name. This would make it possible
to use git format-patch to regenerate the entire quilt patch series
without changing the filename or performing other unnecessary
churn. This is desirable because git tools like interactive rebase are
very powerful for manipulating a patch series, and it would be nice to
be able to use those without unnecessarily renaming all the patches.

(Of course, it would be even nicer to be able to just maintain these
patches in git... but sometimes you really do need them as a patch
series, in which case this ability would come in handy)

(And of course, format-patch still causes some other churn, like adding
the "From HASH DATE" line at the top of the patch and updating the
version number at the bottom, so it would be nice if there were flags to
stop it from adding those as well)

I can write patches to add all these features, but I thought it was best
to ask first, since adding a new pseudo-header/trailer might be a
radical step. I could alternatively do all of this with some local bash
scripts wrapping quiltimport and format-patch, but I think these
features might be useful to others too.

Thanks!

                 reply	other threads:[~2015-07-18 20:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87h9p1qljs.fsf@earth.i-did-not-set--mail-host-address--so-tickle-me \
    --to=sbaugh@catern.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 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).