From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] format-patch: add --prefix to prepend a prefix to output file names
Date: Wed, 10 Jun 2009 09:18:00 +1000 [thread overview]
Message-ID: <fcaeb9bf0906091618l406116d8k307f6661b451d030@mail.gmail.com> (raw)
In-Reply-To: <4A2E6407.1010402@viscovery.net>
2009/6/9 Johannes Sixt <j.sixt@viscovery.net>:
> Nguyễn Thái Ngọc Duy schrieb:
>> I use git to manages patches in my Gentoo development. In Gentoo,
>> all ebuilds (another form of RPM spec) corresponding to different
>> versions of the same package are grouped into one directory. So patches
>> for each versions usually have a prefix to separate them from the ones
>> for other versions. With --prefix it comes handy to produce such patches,
>> for example:
>>
>> git format-patch --prefix dbus-1.2.3- HEAD~5
>>
>> will generate patches for dbus-1.2.3 for me, all starting with "dbus-1.2.3-".
>
> Can't you use --output-directory/-o? It is not the same, but almost.
-o seems to put slash at the end (in reopen_stdout()) but I don't want
to create another directory.
--
Duy
prev parent reply other threads:[~2009-06-09 23:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 11:33 [PATCH] format-patch: add --prefix to prepend a prefix to output file names Nguyễn Thái Ngọc Duy
2009-06-09 12:37 ` Andreas Ericsson
2009-06-09 23:14 ` Nguyen Thai Ngoc Duy
2009-06-10 10:28 ` [PATCH] format-patch: add --filename-prefix " Nguyễn Thái Ngọc Duy
2009-06-10 10:51 ` Jakub Narebski
2009-06-10 10:56 ` Nguyen Thai Ngoc Duy
2009-06-10 15:58 ` Junio C Hamano
2009-06-14 7:10 ` Nguyễn Thái Ngọc Duy
2009-06-14 8:25 ` Junio C Hamano
2009-06-14 8:29 ` Stephen Boyd
2009-06-14 8:59 ` Junio C Hamano
2009-06-14 19:46 ` Stephen Boyd
2009-06-14 23:32 ` Nguyen Thai Ngoc Duy
2009-06-09 13:30 ` [PATCH] format-patch: add --prefix " Johannes Sixt
2009-06-09 23:18 ` Nguyen Thai Ngoc Duy [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=fcaeb9bf0906091618l406116d8k307f6661b451d030@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).