From: Timur Tabi <timur@freescale.com>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: git@vger.kernel.org
Subject: Re: How does format-patch determine the filename of the patch?
Date: Thu, 29 Oct 2009 08:05:21 -0500 [thread overview]
Message-ID: <ed82fe3e0910290605j302747f9o6a86acb414427639@mail.gmail.com> (raw)
In-Reply-To: <200910151959.47778.robin.rosenberg.lists@dewire.com>
On Thu, Oct 15, 2009 at 12:59 PM, Robin Rosenberg
<robin.rosenberg.lists@dewire.com> wrote:
>> The reason I ask is that I'm writing a script which calls
>> git-format-patch to create some patches for post-processing. So I
>> need the name of the file that git-format-patch creates so that I can
>> open it and examine it. I'd liked to see if there's a way to get the
>> name of the patch without actually creating the file.
>
> It tells you the names on stdout.
Is there a way for it to tell me the name on stdout *without* actually
creating the patch?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2009-10-29 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 16:17 How does format-patch determine the filename of the patch? Timur Tabi
2009-10-15 17:48 ` Thomas Rast
2009-10-15 17:59 ` Robin Rosenberg
2009-10-29 13:05 ` Timur Tabi [this message]
2009-10-29 13:14 ` Joshua Roys
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=ed82fe3e0910290605j302747f9o6a86acb414427639@mail.gmail.com \
--to=timur@freescale.com \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.com \
/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).