From: Jeff King <peff@peff.net>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] git clone --checkout <branch>
Date: Tue, 16 Feb 2010 06:07:24 -0500 [thread overview]
Message-ID: <20100216110724.GA25173@coredump.intra.peff.net> (raw)
In-Reply-To: <be6fef0d1002160248h7410d4edu6e3ed1fd27c40059@mail.gmail.com>
On Tue, Feb 16, 2010 at 06:48:42PM +0800, Tay Ray Chuan wrote:
> what do you guys think about allowing users to specify the branch to
> checkout when cloning, instead of the default HEAD of the to-be-cloned
> repository?
I think it's a great idea, but that we should call it "--branch" and
that I should travel back in time to implement it last September as
7a4ee28.
-Peff
next prev parent reply other threads:[~2010-02-16 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 10:48 [RFC] git clone --checkout <branch> Tay Ray Chuan
2010-02-16 11:07 ` Jeff King [this message]
2010-02-16 11:12 ` Tay Ray Chuan
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=20100216110724.GA25173@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=rctay89@gmail.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).