From: "Duncan Mak" <duncan@a-chinaman.com>
To: "Alexandre Julliard" <julliard@winehq.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] fix vc git
Date: Fri, 22 Dec 2006 10:17:55 -0500 [thread overview]
Message-ID: <8e745ecf0612220717v5c7b3a02v55b36f865278ea9c@mail.gmail.com> (raw)
In-Reply-To: <87ac1guj9c.fsf@wine.dyndns.org>
On 12/22/06, Alexandre Julliard <julliard@winehq.org> wrote:
>
> OK, but in that case vc-git-registered needs to return failure, you
> cannot call git-ls-files as it may find the file in the wrong
> directory. I'd suggest something like this:
>
Ah, okay. I agree, that is a better patch.
Would you be committing it soon?
Thanks,
Duncan.
prev parent reply other threads:[~2006-12-22 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 11:25 [PATCH] fix vc git Duncan Mak
2006-12-21 11:32 ` Jakub Narebski
2006-12-21 11:59 ` Duncan Mak
2006-12-22 0:52 ` Junio C Hamano
2006-12-22 4:11 ` Duncan Mak
2006-12-22 4:54 ` Junio C Hamano
2006-12-22 12:39 ` Alexandre Julliard
2006-12-22 12:51 ` Duncan Mak
2006-12-22 13:56 ` Alexandre Julliard
2006-12-22 15:17 ` Duncan Mak [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=8e745ecf0612220717v5c7b3a02v55b36f865278ea9c@mail.gmail.com \
--to=duncan@a-chinaman.com \
--cc=git@vger.kernel.org \
--cc=julliard@winehq.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).