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

Re: fixing duplicated history

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 12, 2008, 22:53 UTC
Message-ID
<7vod0klfng.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20081112222346.GA24013@frodo>
Felipe Balbi <me@felipebalbi.com> writes:
Show 9 quoted lines
> 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 ?
>
> If so, would it cause any problems to the users who already cloned the
> original tree ? I mean, will git see it as a different history line and
> try a merge or will it figure it's the same tree with the duplicated
> entries removed ?

I assume that you meant "commit" by "entry", and also I assume that you read "git filter-branch" not "git reflog delete". Then you are right.

And rewriting history with filter-branch will cause problems to the downstream users.

Previous: Robin RosenbergNext: Felipe Balbi
Message 3 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.