Git development
 help / color / mirror / Atom feed
From: Thomas Koch <thomas@koch.ro>
To: Francois-Xavier Le Bail <devel.fx.lebail@orange.fr>
Cc: Philip Oakley <philipoakley@iee.org>,
	Konstantin Khomoutov <kostix+git@007spb.ru>,
	Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	git@vger.kernel.org
Subject: Re: How to rebase when some commit hashes are in some commit messages
Date: Sun, 18 Oct 2015 15:58:25 +0200	[thread overview]
Message-ID: <1634617.ZbHCyji7nE@x121e> (raw)
In-Reply-To: <561F597B.8090102@orange.fr>

On Thursday 15 October 2015 09:44:59 Francois-Xavier Le Bail wrote:
> >> On Tue, 13 Oct 2015 10:50:40 +0200
> >> Francois-Xavier Le Bail <devel.fx.lebail@orange.fr> wrote:
> >>> >> For example, if I rebase the following commits, I would want that
> >>> >> if the commit hash 2222222... become 7777777...,
> >>> >> the message
> >>> >> "Update test output for 2222222222222222222222222222222222222222"
> >>> >> become
> >>> >> "Update test output for 7777777..."
> >>> >> 
> >>> >> Is it possible currently? And if yes how?

The code review system Gerrit (highly recommended!) uses a commit-hook to adds 
a trailer line to every commit message, e.g.:

Change-Id: Id8269a1aa4a2c7a1a584b23b01d63259410c4e85

This Change-Id is used to identify a change even if the change gets amended or 
rebased and thus is represented in a different commit.

So if you're using Gerrit you can refer to changes instead of commits and use 
the Change-Id. Even if you don't use Gerrit you can still use its commit-hook 
to write the Change-Id trailers.

Regards,

Thomas Koch

  parent reply	other threads:[~2015-10-18 14:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 19:59 How to rebase when some commit hashes are in some commit messages Francois-Xavier Le Bail
2015-10-12 20:21 ` Matthieu Moy
2015-10-13  8:50   ` Francois-Xavier Le Bail
2015-10-13 13:00     ` Konstantin Khomoutov
2015-10-13 13:29       ` Philip Oakley
2015-10-13 17:07         ` Jacob Keller
2015-10-13 18:00           ` Mike Rappazzo
2015-10-13 19:24             ` Philip Oakley
2015-10-13 21:28               ` Jacob Keller
2015-10-13 23:06                 ` Philip Oakley
2015-10-15  8:12             ` Francois-Xavier Le Bail
2015-10-15  8:06           ` Francois-Xavier Le Bail
2015-10-15  7:44         ` Francois-Xavier Le Bail
2015-10-15  9:41           ` Johannes Schindelin
2015-10-16  8:01             ` Philip Oakley
2015-10-18 13:58           ` Thomas Koch [this message]
2015-10-18 16:23 ` Ævar Arnfjörð Bjarmason

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=1634617.ZbHCyji7nE@x121e \
    --to=thomas@koch.ro \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=devel.fx.lebail@orange.fr \
    --cc=git@vger.kernel.org \
    --cc=kostix+git@007spb.ru \
    --cc=philipoakley@iee.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