git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: RFC - "git editlog" feature for fixing up local commit messages

From
Nicolas Pitre <nico@fluxnic.net>
Date
Mar 29, 2010, 15:08 UTC
Message-ID
<alpine.LFD.2.00.1003291102250.694@xanadu.home>
In-Reply-To
<fabb9a1e1003290641s27306373k3a2669318a7b67a8@mail.gmail.com>
On Mon, 29 Mar 2010, Sverre Rabbelier wrote:
Show 10 quoted lines
> Heya,
> 
> On Mon, Mar 29, 2010 at 07:31, Eric Raymond <esr@thyrsus.com> wrote:
> > Now, about step 3.  The official git command set only directly supports
> > amending the tip commit.  There is a semi-documented procedure for
> > amending previous commits using an interactive rebase, but trying to
> > understand it makes my brain hurt.  Don't want to go there.
> 
> Go there anyway. These days it's as simple as changing "pick" to
> "reword" on the appropriate commit. Really, give it a try.

While the 'git rebase -i' solution has its place (and I do use it myself), it essentially deals with only one branch while having a filter-branch based solution allows for such changes to be applied globally i.e. to all branches in the presence of history fork points.

Nicolas
Previous: Sverre RabbelierNext: Avery Pennarun
Message 3 of 8 in “RFC - "git editlog" feature for fixing up local commit messages”
  1. Eric RaymondMar 29, 2010
  2. Sverre RabbelierMar 29, 2010
  3. Nicolas PitreMar 29, 2010
  4. Avery PennarunMar 29, 2010
  5. Michael J GruberMar 30, 2010
  6. Avery PennarunMar 30, 2010
  7. Jonathan NiederMar 30, 2010
  8. Miles BaderMar 30, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.