From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2011, #14; Tue, 31)
Date: Wed, 01 Jun 2011 08:52:51 +0200 [thread overview]
Message-ID: <4DE5E1C3.8000904@viscovery.net> (raw)
In-Reply-To: <7vhb8aij91.fsf@alter.siamese.dyndns.org>
Am 6/1/2011 0:43, schrieb Junio C Hamano:
> * ef/maint-win-verify-path (2011-05-27) 3 commits
> - verify_path: consider dos drive prefix
> - real_path: do not assume '/' is the path seperator
> - A Windows path starting with a backslash is absolute
>
> J6t had a reasonable question in the discussion; has it been resolved?
This particular question is resolved; I consider "verify_path: consider
dos drive prefix" a good change. But I haven't had a chance to review the
effects of the other two changes, yet.
-- Hannes
next prev parent reply other threads:[~2011-06-01 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 22:43 What's cooking in git.git (May 2011, #14; Tue, 31) Junio C Hamano
2011-06-01 6:52 ` Johannes Sixt [this message]
2011-06-01 19:21 ` 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=4DE5E1C3.8000904@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).