From: Junio C Hamano <gitster@pobox.com>
To: dturner@twopensource.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH v7 0/3]
Date: Tue, 12 May 2015 22:51:59 -0700 [thread overview]
Message-ID: <xmqqoalpautc.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1431481799-23560-1-git-send-email-dturner@twopensource.com> (dturner@twopensource.com's message of "Tue, 12 May 2015 21:49:56 -0400")
dturner@twopensource.com writes:
> This version of the patch adds improved error outputs for various
> weird situations that can come up during symlink resolution.
Overall these looked sensible. I have been resisting the temptation
to merge this to my tree since around v5, primarily because I did
not want to resolve merge conflicts with kn/cat-file-literally more
than once, but I think this version looks solid enough that whatever
rerere will remember will be applicable to later iteration if one is
ever needed.
Hence I queued it on 'pu' for now; I haven't checked how the doc
formats, though.
Thanks.
next prev parent reply other threads:[~2015-05-13 5:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 1:49 [PATCH v7 0/3] dturner
2015-05-13 1:49 ` [PATCH v7 1/3] tree-walk: learn get_tree_entry_follow_symlinks dturner
2015-05-13 15:39 ` Jeff King
2015-05-13 1:49 ` [PATCH v7 2/3] sha1_name: get_sha1_with_context learns to follow symlinks dturner
2015-05-13 1:49 ` [PATCH v7 3/3] cat-file: add --follow-symlinks to --batch dturner
2015-05-13 3:57 ` Junio C Hamano
2015-05-13 5:51 ` Junio C Hamano [this message]
[not found] <"<CAC05386q2iGoiJ_fRgwoOTF23exEN2D1+oh4VjajEvYQ58O1TQ@mail.gmail.com>
2018-09-27 15:13 ` [PATCH] branch: colorize branches checked out in a linked working tree the same way as the current branch is colorized Nickolai Belakovski
2019-02-01 22:04 ` [PATCH v7 0/3] nbelakovski
2019-02-01 22:28 ` Junio C Hamano
2019-02-01 23:31 ` Nickolai Belakovski
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=xmqqoalpautc.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=dturner@twopensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.