git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
	"Johannes Sixt" <j6t@kdbg.org>,
	"Ramsay Jones" <ramsay@ramsay1.demon.co.uk>,
	"Yue Lin Ho" <yuelinho777@gmail.com>,
	git@vger.kernel.org, "Michael Haggerty" <mhagger@alum.mit.edu>
Subject: [PATCH v4 0/1] Use absolute paths of lockfiles
Date: Sat,  6 Sep 2014 12:31:28 +0200	[thread overview]
Message-ID: <1409999489-25193-1-git-send-email-mhagger@alum.mit.edu> (raw)
In-Reply-To: CACsJy8AJvt3bVj783eyHhiFaMD3Ys6pAsyT7S2TYi2a_ACKcRg@mail.gmail.com

This patch applies on top of the patch series that I just sent [1]:

    Lockfile correctness and refactoring, v4

It has the same effect as Duy's [2]

    Keep .lock file paths absolute, v3

except that my patch series obviates the need for his patches 1/3 and
2/3. So only one patch remains, the equivalent of his patch 3/3,
simplified because lockfile::filename is now a strbuf.

So I've shamelessly labeled this "v4" of his patch series and I've
left Duy as the author, because his commit message (which I used
directly) has far more intellectual content than the code change. Duy,
if that's not OK with you, please let me know.

Michael

[1] http://thread.gmane.org/gmane.comp.version-control.git/256564
[2] http://thread.gmane.org/gmane.comp.version-control.git/253817/focus=254573

Nguyễn Thái Ngọc Duy (1):
  lockfile.c: store absolute path

 lockfile.c                    | 14 +++++++++++---
 t/t2107-update-index-basic.sh | 15 +++++++++++++++
 2 files changed, 26 insertions(+), 3 deletions(-)

-- 
2.1.0

  reply	other threads:[~2014-09-06 10:31 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   ` Michael Haggerty [this message]
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
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=1409999489-25193-1-git-send-email-mhagger@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=pclouds@gmail.com \
    --cc=ramsay@ramsay1.demon.co.uk \
    --cc=yuelinho777@gmail.com \
    /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).