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

Re: Add "git-update-ref" to update the HEAD (or other) ref

From
Linus Torvalds <torvalds@osdl.org>
Date
Sep 26, 2005, 00:50 UTC
Message-ID
<Pine.LNX.4.58.0509251747290.3308@g5.osdl.org>
In-Reply-To
<7vhdc8n2xb.fsf@assigned-by-dhcp.cox.net>
On Sun, 25 Sep 2005, Junio C Hamano wrote:
Show 6 quoted lines
> 
> I'd like to take these patches in two stages (I am not asking
> you for a resend):
> 
>  - Drop the emulated symlink part from the update-ref.c; have it
>    graduate to "master" branch and use it in existing scripts.
Sure.
Show 5 quoted lines
>  - Take the read_ref() change, along with a patch to re-add the
>    emulated symlink part to update-ref.c (after making its
>    interpretation to match that of read_ref() -- which requires
>    the prefix to be exactly "ref: " five bytes); keep it in "pu"
>    branch a bit longer.

I was actually thinking of maybe entirely replacing "read_ref()" with the more powerful "resolve_ref()" - moving resolve_ref() into refs.c.

That way there's only one place that knows about the "ref:" thing.

But yes, forcing the format to be "ref: " instead of "ref:<whitespace>*" sounds fine.

		Linus
Previous: Junio C HamanoNext: Junio C Hamano
Message 17 of 19 in “Add "git-update-ref" to update the HEAD (or other) ref”
  1. Linus TorvaldsSep 25, 2005
  2. Linus TorvaldsSep 25, 2005
  3. Junio C HamanoSep 25, 2005
  4. Use git-update-ref in scripts.Junio C Hamano, Sep 28, 2005
  5. Linus TorvaldsSep 28, 2005
  6. Junio C HamanoSep 28, 2005
  7. Linus TorvaldsSep 28, 2005
  8. Junio C HamanoSep 28, 2005
  9. Linus TorvaldsSep 28, 2005
  10. Junio C HamanoSep 28, 2005
  11. Linus TorvaldsSep 29, 2005
  12. Junio C HamanoSep 28, 2005
  13. Junio C HamanoSep 28, 2005
  14. Fredrik KuivinenSep 28, 2005
  15. Linus TorvaldsSep 29, 2005
  16. Junio C HamanoSep 25, 2005
  17. Linus TorvaldsSep 26, 2005
  18. Junio C HamanoSep 26, 2005
  19. Linus TorvaldsSep 26, 2005

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.