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

changing history once public

From
JFJohn J. Franey <jjfraney@gmail.com>
Date
May 30, 2008, 21:24 UTC
Message-ID
<1212182690.8311.30.camel@isidore.myhome.westell.com>

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 I want to keep this branch current (in public), I would pull from the tracking branch resolve conflicts and push to my public repo. 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?

I think the downside of not keeping my branch current is that I'd be handing off to my colleagues the task of resolving merge conflicts. Is that right?

Thanks, John

Next: Jon Loeliger
Message 1 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.