git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: Kevin Ballard <kevin@sb.org>, git list <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] rebase: pass --signoff option to git am
Date: Mon, 6 Dec 2010 11:28:47 -0600	[thread overview]
Message-ID: <20101206172847.GA6272@burratino> (raw)
In-Reply-To: <AANLkTinnn_QnBJ8AZT9ZB+ZHVRDZV0tDret=YQeyfa01@mail.gmail.com>

Giuseppe Bilotta wrote:

> For what it's worth, somebody on #git just asked how to signoff a
> bunch of patches. The answer was to rebase -i and sign off each one of
> them.

How I would do it in existing git:

	git branch oldhead
	git reset --keep base
	git log --oneline --graph HEAD..oldhead;	# the right patches?
	git cherry-pick -s HEAD..oldhead
	git diff oldhead

Or without multiple-cherry-pick, maybe:

	git branch oldhead
	git reset --keep base
	git format-patch -k --stdout HEAD..oldhead >series
	git am -s -3 -i series;	# the right patches?
	git diff oldhead

No opinion on the automatic-signoff-in-rebase here.

  reply	other threads:[~2010-12-06 17:29 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
2010-12-06 10:41     ` Giuseppe Bilotta
2010-12-06 17:28       ` Jonathan Nieder [this message]
  -- 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=20101206172847.GA6272@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=giuseppe.bilotta@gmail.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).