From: Tay Ray Chuan <rctay89@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] don't append 'opaquelocktoken:' in PUT and MOVE
Date: Sun, 8 Feb 2009 03:00:58 +0800 [thread overview]
Message-ID: <be6fef0d0902071100o68cf0f81m2e666bb1dac9977a@mail.gmail.com> (raw)
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
next prev parent reply other threads:[~2009-02-07 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 15:12 [PATCH] don't append 'opaquelocktoken:' in PUT and MOVE Tay Ray Chuan
2009-02-07 17:03 ` Johannes Schindelin
2009-02-07 17:52 ` Tay Ray Chuan
2009-02-07 18:04 ` Johannes Schindelin
2009-02-07 18:38 ` Tay Ray Chuan
2009-02-07 18:57 ` Johannes Schindelin
2009-02-07 19:00 ` Tay Ray Chuan [this message]
2009-02-07 19:43 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be6fef0d0902071100o68cf0f81m2e666bb1dac9977a@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).