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

Re: RFC: reflog for deleted branches

From
Junio C Hamano <gitster@pobox.com>
Date
May 3, 2012, 21:37 UTC
Message-ID
<7vaa1pdjz8.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4FA2F7DA.6020108@tu-clausthal.de>
Sven Strickroth <sven.strickroth@tu-clausthal.de> writes:
Show 8 quoted lines
> an often heart question is how to restore deleted branches. Sometimes
> those can be restored by using the reflog of the HEAD.
>
> But why not create a special (ref)log for deleted branches (with SHA1,
> date, name of the branch and maybe commit message of the last commit on
> the deleted branch)? This way people could just look up the SHA1 of the
> deleted branch and can recreate it (even if they moved the HEAD around a
> lot).

The itch is legit, but I doubt a "special log for deleted branches" is a good design. Why do you limit yourself only to a single "last" commit? Wouldn't it be a better design to save away the entire reflog for the branch when a branch is deleted, possibly with expedited expire rule for such a reflog?

Previous: Sven StrickrothNext: Sven Strickroth
Message 2 of 9 in “RFC: reflog for deleted branches”
  1. Sven StrickrothMay 3, 2012
  2. Junio C HamanoMay 3, 2012
  3. Sven StrickrothMay 3, 2012
  4. Junio C HamanoMay 3, 2012
  5. Sven StrickrothMay 3, 2012
  6. Robin RosenbergMay 4, 2012
  7. Junio C HamanoMay 4, 2012
  8. Andrew SayersMay 3, 2012
  9. Sitaram ChamartyMay 4, 2012

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.