From: Steffen Prohaska <prohaska@zib.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] rebase: add --signoff option
Date: Sun, 30 Sep 2007 23:38:27 +0200 [thread overview]
Message-ID: <C94CC989-096D-43B5-BA16-DBD4D84038C0@zib.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0709302229320.28395@racer.site>
On Sep 30, 2007, at 11:30 PM, Johannes Schindelin wrote:
> On Sun, 30 Sep 2007, Steffen Prohaska wrote:
>
>> When preparing a series of commits for upstream you may
>> need to signoff commits if you forgot to do so earlier.
>
> Why not use format-patch's --signoff option for that?
format-patch is fine for mail. But if I either push the commits
to a shared repo (like msysgit's mob) or ask upstream to pull
from my public repo format-patch doesn't help directly.
Steffen
next prev parent reply other threads:[~2007-09-30 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 16:15 [PATCH] rebase: add --signoff option Steffen Prohaska
2007-09-30 21:30 ` Johannes Schindelin
2007-09-30 21:38 ` Steffen Prohaska [this message]
2007-09-30 21:41 ` Johannes Schindelin
2007-10-01 4:59 ` Steffen Prohaska
2007-10-01 8:20 ` Junio C Hamano
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=C94CC989-096D-43B5-BA16-DBD4D84038C0@zib.de \
--to=prohaska@zib.de \
--cc=Johannes.Schindelin@gmx.de \
--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).