From: MikeW <mw_phil@yahoo.co.uk>
To: git@vger.kernel.org
Subject: feature request: git format-patch - allow --suffix to work with --numbered-files
Date: Wed, 16 Nov 2011 13:02:52 +0000 (UTC) [thread overview]
Message-ID: <loom.20111116T135509-236@post.gmane.org> (raw)
"Numbered files" is good for creating patches with uniform filenames, rather
than verbose filenames containing part of the commit message, but if working for
example with submodules, there is possible name collision if pooling the patches
in one place.
I thought that --suffix=$name would be a good way to disambiguate but found that
--numbered-files wins and kills any suffix.
Hence suggestion that --suffix used with --numbered-files is allowed to generate
a filename suffix as it does when not in "numbered files" mode.
In the absence of a --suffix command, the behaviour would be as now.
reply other threads:[~2011-11-16 13:15 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=loom.20111116T135509-236@post.gmane.org \
--to=mw_phil@yahoo.co.uk \
--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).