Re: How to rebase when some commit hashes are in some commit messages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx> 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


--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]