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

Re: Editing Git Log

From
Björn Steinbrink <b.steinbrink@gmx.de>
Date
Sep 18, 2008, 06:21 UTC
Message-ID
<20080918062116.GB32670@atjola.homenet>
In-Reply-To
<48D1F19E.60907@panasas.com>
On 2008.09.18 09:13:50 +0300, Boaz Harrosh wrote:
Show 21 quoted lines
> Piet Delaney wrote:
> > I think I recall reading that a feature of git was the prevention of the 
> > git commits
> > from being changed. I noticed today that a couple of us have checked in 
> > files
> > without our customary [XTENSA] architecture prefixed to the 1st line of our
> > Commit Messages.
> > 
> > I couldn't find a way to do this, other than our reverting back to a 
> > earlier repository
> > and recommitting (each?) change with the slightly changed Commit Message;
> > not an attractive investment of our time.
> > 
> > Any suggestions?
> > 
> > -piet
> > --
> 
> git rebase --interactive FIRST_BAD_COMMIT^ will effectively do the same
> as above but in a nice automated way. Just change pick => edit on these
> patches that need fixing, you'll see.
git filter-branch with a suited msg-filter is even more automated :-)
Björn
Previous: Boaz HarroshNext: Matthias Kestenholz
Message 3 of 4 in “Editing Git Log”
  1. Piet DelaneySep 18, 2008
  2. Boaz HarroshSep 18, 2008
  3. Björn SteinbrinkSep 18, 2008
  4. Matthias KestenholzSep 18, 2008

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.