From: Junio C Hamano <gitster@pobox.com>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: Pierre Habouzit <madcoder@debian.org>, Git ML <git@vger.kernel.org>
Subject: Re: [PATCH 1/2 v3] renaming quote_path() as quote_path_relative()
Date: Sat, 08 Mar 2008 12:31:10 -0800 [thread overview]
Message-ID: <7vabl9t0tt.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1205004816-28301-1-git-send-email-dpotapov@gmail.com> (Dmitry Potapov's message of "Sat, 8 Mar 2008 22:33:35 +0300")
I think our mails and works crossed. Please check what is in 'next',
where I already applied the previous ones with trivial fix-ups and an
additional test.
prev parent reply other threads:[~2008-03-08 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7vbq5r5czw.fsf@gitster.siamese.dyndns.org>
2008-03-08 19:33 ` [PATCH 1/2 v3] renaming quote_path() as quote_path_relative() Dmitry Potapov
2008-03-08 19:33 ` [PATCH 2/2] git-clean: correct printing relative path Dmitry Potapov
2008-03-08 20:31 ` Junio C Hamano [this message]
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=7vabl9t0tt.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.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).