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

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

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 7, 2009, 18:04 UTC
Message-ID
<alpine.DEB.1.00.0902071903020.10279@pacific.mpi-cbg.de>
In-Reply-To
<be6fef0d0902070952l5818e4b7x3048c667661ce31@mail.gmail.com>
Hi,
On Sun, 8 Feb 2009, Tay Ray Chuan wrote:
Show 9 quoted lines
> On Sun, Feb 8, 2009 at 1:03 AM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
> 
> > Besides, I have to wonder where request->lock->token is set, and if 
> > that would not be the better place to fix the issue?
> 
> Are you suggesting perhaps that we revert commit 753bc91? Or perhaps 
> create another way to access lock tokens, say, get_lock_token(int 
> prepend_scheme)?
I do not suggest anything like that.

But I _refuse_ to go and investigate a thing that you should know already, and that you should be able to defend, indeed, something you should have defended in the commit message:

Why does request->lock->token have the prefix at all?

Ciao, Dscho

Previous: Tay Ray ChuanNext: Tay Ray Chuan
Message 4 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.