[Top][All Lists]

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

Re: Should we restore manually maintained ChangeLogs

From: Sven Axelsson
Subject: Re: Should we restore manually maintained ChangeLogs
Date: Thu, 10 Mar 2016 12:49:34 +0100

On 10 March 2016 at 11:34, Eli Zaretskii <address@hidden> wrote:
>> From: Andreas Schwab <address@hidden>
>> Cc: address@hidden
>> Date: Thu, 10 Mar 2016 11:00:47 +0100
>> > More generally, can we put something in .git/config that would cause
>> > that namespace to be pulled by default?
>> git config --add remote.origin.fetch +refs/replace/*:refs/replace/*
> OK, thanks.
> So how does one go about creating a replacement commit for a commit
> that was pushed upstream?  The man page of "git replace" mentions "git
> rebase", but I cannot find anything pertinent on the rebase man page.
> The procedure described here:
>   https://git-scm.com/book/en/v2/Git-Tools-Replace
> sounds quite complicated.  If we need to do all that every time we
> want to fix a single commit, I'd expect a lot of mistakes and snafus.
> But maybe there's an easier way, in which case we could consider this
> feature as part of the solution for fixing mistakes in log messages.

When you only want to deal with changing the commit message and not
the actual commit, it is as simple as calling `git replace --edit
<SHA>'. This will bring up your system editor where you can change the
commit message.

Doing it this way will not change history.

Sven Axelsson

reply via email to

[Prev in Thread] Current Thread [Next in Thread]