From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Kevin Ballard <kevin@sb.org>
Cc: git list <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] rebase: pass --signoff option to git am
Date: Tue, 30 Nov 2010 09:09:42 +0100 [thread overview]
Message-ID: <AANLkTindvz=7OmYaL6AL_oAj50U9PLnRrbSpjgR92z7C@mail.gmail.com> (raw)
In-Reply-To: <ADC46761-DFF5-486D-B604-05BA8C8631EB@sb.org>
On Mon, Nov 29, 2010 at 11:57 PM, Kevin Ballard <kevin@sb.org> wrote:
> On Nov 27, 2010, at 3:15 AM, Giuseppe Bilotta wrote:
>
>> This allows people (like me) that forget to sign off their commits to do
>> a single rebase pass e.g. while preparing the patchset for submission.
>
> You're probably already aware, but git format-patch supports the -s/--signoff
> flags to sign off commits as they're prepared. There's even a config var
> you can set to make this the default (format.signoff = true).
That works if you're sharing your patches with format-patch, but not
for example when asking for a pull. Maybe I should extend the commit
message to include this case.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2010-11-30 8:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 11:15 [PATCH] rebase: pass --signoff option to git am Giuseppe Bilotta
2010-11-28 0:32 ` Sverre Rabbelier
2010-11-27 19:05 ` Martin von Zweigbergk
2010-11-28 8:00 ` Giuseppe Bilotta
2010-11-29 22:57 ` Kevin Ballard
2010-11-30 8:09 ` Giuseppe Bilotta [this message]
2010-12-06 10:41 ` Giuseppe Bilotta
2010-12-06 17:28 ` Jonathan Nieder
-- strict thread matches above, loose matches on Subject: below --
2017-01-21 10:49 Giuseppe Bilotta
2017-01-23 18:13 ` Junio C Hamano
2017-01-23 20:03 ` Giuseppe Bilotta
2017-01-23 20:16 ` Junio C Hamano
2017-01-23 22:35 ` Giuseppe Bilotta
2017-01-23 23:27 ` Junio C Hamano
2017-01-24 7:06 ` Giuseppe Bilotta
2017-01-26 18:18 ` Giuseppe Bilotta
2010-09-16 9:07 Giuseppe Bilotta
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='AANLkTindvz=7OmYaL6AL_oAj50U9PLnRrbSpjgR92z7C@mail.gmail.com' \
--to=giuseppe.bilotta@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kevin@sb.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).