From: Yue Lin Ho <yuelinho777@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH v4 0/1] Use absolute paths of lockfiles
Date: Tue, 9 Sep 2014 18:47:07 -0700 (PDT) [thread overview]
Message-ID: <1410313627634-7618314.post@n2.nabble.com> (raw)
In-Reply-To: <CACsJy8BNSriBAYkdKHEJa3wN_pcFkjzsOUw_1kyMPz0J_2KD+A@mail.gmail.com>
Hi Duy, Michael, Junio C Hamano:
Thanks for working on lock file issue.
Thank you! Thank you~
^_^
Yue Lin Ho
--
View this message in context: http://git.661346.n2.nabble.com/What-s-cooking-in-git-git-Aug-2014-02-Fri-8-tp7616651p7618314.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2014-09-10 1:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 22:18 What's cooking in git.git (Aug 2014, #02; Fri, 8) Junio C Hamano
2014-08-08 23:44 ` Duy Nguyen
2014-09-06 10:31 ` [PATCH v4 0/1] Use absolute paths of lockfiles Michael Haggerty
2014-09-06 10:31 ` [PATCH v4 1/1] lockfile.c: store absolute path Michael Haggerty
2014-09-06 13:30 ` [PATCH v4 0/1] Use absolute paths of lockfiles Duy Nguyen
2014-09-10 1:47 ` Yue Lin Ho [this message]
2014-10-15 2:44 ` Yue Lin Ho
2014-08-09 20:01 ` What's cooking in git.git (Aug 2014, #02; Fri, 8) Charles Bailey
2014-08-10 2:42 ` Jeff King
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=1410313627634-7618314.post@n2.nabble.com \
--to=yuelinho777@gmail.com \
--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).