From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Theo Niessink <theo@taletn.com>,
Erik Faye-Lund <kusmabite@gmail.com>
Subject: Re: What's cooking in git.git (Jun 2011, #01; Sun, 5)
Date: Mon, 06 Jun 2011 09:16:57 +0200 [thread overview]
Message-ID: <4DEC7EE9.9060807@viscovery.net> (raw)
In-Reply-To: <7vsjrna2x2.fsf@alter.siamese.dyndns.org>
Am 6/6/2011 8:29, schrieb Junio C Hamano:
> * ef/maint-win-verify-path (2011-05-27) 3 commits
> (merged to 'next' on 2011-06-01 at f316f68)
> + verify_path: consider dos drive prefix
> + real_path: do not assume '/' is the path seperator
> + A Windows path starting with a backslash is absolute
>
> Will cook a bit longer.
I agree to all changes. There was a bit of back-and-forth about the
"verify_path" change. Erik, Theo, would you please check whether the
queued version is the one you finally agreed on?
-- Hannes
next prev parent reply other threads:[~2011-06-06 7:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 6:29 What's cooking in git.git (Jun 2011, #01; Sun, 5) Junio C Hamano
2011-06-06 7:16 ` Johannes Sixt [this message]
2011-06-06 7:38 ` Erik Faye-Lund
2011-06-07 18:21 ` Jamey Sharp
2011-06-07 18:21 ` [PATCH 1/4] Fix prefix handling in ref iteration functions Jamey Sharp
2011-06-07 18:21 ` [PATCH 2/4] Add infrastructure for ref namespaces Jamey Sharp
2011-06-07 19:12 ` Bert Wesarg
2011-06-07 22:25 ` Josh Triplett
2011-06-07 18:21 ` [PATCH 3/4] Support ref namespaces for remote repositories via upload-pack and receive-pack Jamey Sharp
2011-06-07 18:21 ` [PATCH 4/4] Add documentation for ref namespaces Jamey Sharp
2011-08-23 10:38 ` Ævar Arnfjörð Bjarmason
2011-08-23 17:19 ` Junio C Hamano
2011-08-24 12:30 ` Ævar Arnfjörð Bjarmason
2011-09-16 0:22 ` Re* " Junio C Hamano
2011-09-16 3:40 ` Jamey Sharp
2011-09-16 16:20 ` Junio C Hamano
2011-06-07 18:59 ` What's cooking in git.git (Jun 2011, #01; Sun, 5) 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=4DEC7EE9.9060807@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kusmabite@gmail.com \
--cc=theo@taletn.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 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.