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

Re: [PATCH 2/2] http-push: remove MOVE step after PUT when sending objects to server

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 18, 2009, 00:48 UTC
Message-ID
<7viqod5thi.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<be6fef0d0901171224y35c3d95cn2d38639ac03c3b8f@mail.gmail.com>
"Ray Chuan" <rctay89@gmail.com> writes:
Show 15 quoted lines
> Currently, git PUTs to
>
>  /repo.git/objects/1a/1a2b...9z_opaquelocktoken:1234-....
>
> then MOVEs to
>
>  /repo.git/objects/1a/1a2b...9z
>
> This is needless. In fact, the only time MOVE requests are sent is for
> this sole purpose (ie. of renaming an object).
>
> A concern raised was repository corruption in the event of failure
> during PUT. "put && move" won't afford any more protection than using
> simply "put", since info/refs is not updated if a PUT fails, so there
> is no cause for concern.

That's a completely bogus reasoning. Normal operation inside the repository that was pushed into won't look at info/refs at all.

The true reason you want to avoid put-then-move is...?
Previous: Ray ChuanNext: Ray Chuan
Message 2 of 10 in “http-push: remove MOVE step after PUT when sending objects to server”
  1. 2/2 http-push: remove MOVE step after PUT when sending objects to serverRay Chuan, Jan 17, 2009
  2. Junio C HamanoJan 18, 2009
  3. Ray ChuanJan 18, 2009
  4. Johannes SchindelinJan 18, 2009
  5. Junio C HamanoJan 18, 2009
  6. Johannes SchindelinJan 18, 2009
  7. Junio C HamanoJan 18, 2009
  8. Johannes SchindelinJan 18, 2009
  9. Sverre RabbelierJan 19, 2009
  10. Junio C HamanoJan 19, 2009

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.