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

Re: [PATCH] don't append 'opaquelocktoken:' in PUT and MOVE

From
Tay Ray Chuan <rctay89@gmail.com>
Date
Feb 7, 2009, 19:00 UTC
Message-ID
<be6fef0d0902071100o68cf0f81m2e666bb1dac9977a@mail.gmail.com>
In-Reply-To
<alpine.DEB.1.00.0902071956480.10279@pacific.mpi-cbg.de>
Hi,

On Sun, Feb 8, 2009 at 2:57 AM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

> Huh?  What does that mean?  Does lock->token have that prefix (including
> the colon) or not?

Yes, it does have the prefix with colon, but it is not true that it is always "opaquelocktoken:" -- it could be some other URI scheme.

I submitting a new patch that accounts for this (other URI schemes).
-- 
Cheers,
Ray Chuan
Previous: Johannes SchindelinNext: Junio C Hamano
Message 7 of 8 in “don't append 'opaquelocktoken:' in PUT and MOVE”
  1. don't append 'opaquelocktoken:' in PUT and MOVETay Ray Chuan, Feb 7, 2009
  2. Johannes SchindelinFeb 7, 2009
  3. Tay Ray ChuanFeb 7, 2009
  4. Johannes SchindelinFeb 7, 2009
  5. Tay Ray ChuanFeb 7, 2009
  6. Johannes SchindelinFeb 7, 2009
  7. Tay Ray ChuanFeb 7, 2009
  8. Junio C HamanoFeb 7, 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.