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

Re: changing history once public

From
Jon Loeliger <jdl@freescale.com>
Date
May 30, 2008, 21:37 UTC
Message-ID
<4840738F.2070909@freescale.com>
In-Reply-To
<1212182690.8311.30.camel@isidore.myhome.westell.com>
John J. Franey wrote:
Show 5 quoted lines
> I think I understand the issue with changing history on branches that
> have been made public.
> 
> What is the negative of publishing a branch and not being able to apply
> history changing commands?

If there is something in that history you want to "remove", it must be done as an inverse patch, or an additional "removal" patch. You can't just change the history by backing it up and writing it differently.

> If I want to keep this branch current (in public), I would pull from the
> tracking branch resolve conflicts and push to my public repo. 
Right.
> This
> action leaves my commit as the parent of another commit; it is not
> longer at HEAD.  Does it matter if my commit is no longer HEAD of my
> branch?

Uh, by definition HEAD is the current-most commit on your active branch, right?

HTH, jdl

Previous: John J. Franey
Message 2 of 2 in “changing history once public”
  1. John J. FraneyMay 30, 2008
  2. Jon LoeligerMay 30, 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.