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

Re: [PATCH v2 2/2] Make old sha1 optional with git update-ref -d

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 3, 2008, 19:39 UTC
Message-ID
<7v3anu2tqs.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080603064957.GA6701@diana.vm.bytemark.co.uk>
Karl Hasselström <kha@treskal.com> writes:
Show 7 quoted lines
> I need this from time to time when experimenting with StGit -- or,
> more precisely, when cleaning up afterwards in case it didn't go so
> well. Packed refs means I can't safely just edit/delete files under
> .git/refs anymore, so I use update-ref instead. And having to use the
> safety belt every time is just plain tedious. I'd say this is a
> perfect example of when using the plumbing by hand is really what you
> want.
Oh, I should have guessed, and I am relieved by your answer.

I was worried that in some workflow people may have to use "update-ref -d" all the time because our Porcelain allows them to create some ref without giving a clean way to remove it (e.g. "branch" and "tag" allow creation and deletion with -d/-D, so they are Ok, but I was worried there might be something else I overlooked).

Manually cleaning up what an experimental version of Porcelain left behind does not fall into category of "normal user has to do this all the time", so I do not have to worry.

Thanks.
Previous: Karl Hasselström
Message 6 of 6 in “Make old sha1 optional with git update-ref -d”
  1. 0/2 Make old sha1 optional with git update-ref -dKarl Hasselström, Jun 2, 2008
  2. 1/2 Clean up builtin-update-ref's option parsingKarl Hasselström, Jun 2, 2008
  3. 2/2 Make old sha1 optional with git update-ref -dKarl Hasselström, Jun 2, 2008
  4. Junio C HamanoJun 3, 2008
  5. Karl HasselströmJun 3, 2008
  6. Junio C HamanoJun 3, 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.