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

Re: fixing duplicated history

From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date
Nov 12, 2008, 22:52 UTC
Message-ID
<200811122352.57476.robin.rosenberg.lists@dewire.com>
In-Reply-To
<20081112222346.GA24013@frodo>
onsdag 12 november 2008 23:23:51 skrev Felipe Balbi:
Show 6 quoted lines
> Hi,
> 
> I have a git tree which history is completely messed up with duplicated
> entries. By reading git man pages I saw that it might be possible to
> delete those duplicated entries with git reflog delete, am I reading it
> right ?

No. The reflog is not the history, except your very local log of what the heads pointed to. You do not see the reflog unless you ask for it, and nobody else can see it (i.e. *your* reflog).

What looks like duplicate entries may commit that have been cherry picked into one or more branches that have been merged thereafter. If you look carefully they have different id's.

-- robin
Previous: Felipe BalbiNext: Junio C Hamano
Message 2 of 4 in “fixing duplicated history”
  1. Felipe BalbiNov 12, 2008
  2. Robin RosenbergNov 12, 2008
  3. Junio C HamanoNov 12, 2008
  4. Felipe BalbiNov 12, 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.