From: "Ping Yin" <pkufranky@gmail.com>
To: "Daniel Barkalow" <barkalow@iabervon.org>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: [RFC PATCH 1/3] Add "vcs" config option in remotes
Date: Mon, 12 Jan 2009 09:29:01 +0800 [thread overview]
Message-ID: <46dff0320901111729y3869db2bxcc2b66a7be247d0b@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0901110332580.19665@iabervon.org>
On Mon, Jan 12, 2009 at 4:12 AM, Daniel Barkalow <barkalow@iabervon.org> wrote:
> This will indicate to programs using the remote that it should be
> accessed through a VCS helper. Until programs support it, have them
> fail it the option is set.
s/it/if/ ?
next prev parent reply other threads:[~2009-01-12 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 20:12 [RFC PATCH 1/3] Add "vcs" config option in remotes Daniel Barkalow
2009-01-12 1:29 ` Ping Yin [this message]
2009-01-12 1:32 ` Daniel Barkalow
2009-01-12 9:52 ` Bert Wesarg
2009-01-12 17:25 ` Daniel Barkalow
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=46dff0320901111729y3869db2bxcc2b66a7be247d0b@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=barkalow@iabervon.org \
--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).