From: Felipe Contreras <felipe.contreras@gmail.com>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] git-clone: Add option --branch to override initial branch
Date: Mon, 9 Mar 2009 18:01:54 +0200 [thread overview]
Message-ID: <94a0d4530903090901o6e8c2a40k676387f90ee461b3@mail.gmail.com> (raw)
In-Reply-To: <loom.20090309T143413-334@post.gmane.org>
On Mon, Mar 9, 2009 at 4:39 PM, Paolo Ciarrocchi
<paolo.ciarrocchi@gmail.com> wrote:
> Junio C Hamano <gitster <at> pobox.com> writes:
>
>>
>> Tor Arne Vestbø <torarnv <at> gmail.com> writes:
>>
>> > The options --branch and -b allow the user to override the initial
>> > branch created and checked out by git-clone (normally this is the
>> > active branch of the remote repository).
>> >
>> > If the selected branch is not found the operation aborts.
>> >
>> > Signed-off-by: Tor Arne Vestbø <torarnv <at> gmail.com>
>>
>> The semantics and desirability of the new feature have been already
>> discussed, and I am not convinced that it is necessary, in the sense that
>> I do not think I likely ever use this myself, but I am just one of git
>> users so that is not a strong basis for rejection.
>
> I wrote a comment about the --branch approach a couple of days ago, dunno why
> but this thread never reached my inbox (replying via gmame web interface).
>
> http://thread.gmane.org/gmane.comp.version-control.git/112527
>
> As I wrote in my post a friend of mine, new to git, was looking for the
> possibility of cloning a repo and automatically checkout a specific branch.
Yeah, I also would like this option... one-liner for people that don't
know git at all.
me: you want my code? just run this command.
--
Felipe Contreras
next prev parent reply other threads:[~2009-03-09 16:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 22:11 [PATCH] git-clone: Add option --branch to override initial branch Tor Arne Vestbø
2009-03-02 23:48 ` Johannes Schindelin
2009-03-03 0:09 ` Junio C Hamano
2009-03-03 0:11 ` Tor Arne Vestbø
2009-03-03 0:33 ` [PATCH v2] " Tor Arne Vestbø
2009-03-03 9:07 ` Johannes Schindelin
2009-03-03 16:47 ` Tor Arne Vestbø
2009-03-03 16:51 ` Junio C Hamano
2009-03-03 17:04 ` Tor Arne Vestbø
2009-03-03 17:07 ` Junio C Hamano
2009-03-04 6:55 ` Junio C Hamano
2009-03-04 8:56 ` Johannes Schindelin
2009-03-04 10:23 ` Tor Arne Vestbø
2009-03-09 14:39 ` Paolo Ciarrocchi
2009-03-09 16:01 ` Felipe Contreras [this message]
2009-03-11 8:52 ` Paolo Ciarrocchi
2009-03-12 4:18 ` Miles Bader
2009-03-12 8:48 ` Paolo Ciarrocchi
2009-03-12 9:12 ` Felipe Contreras
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=94a0d4530903090901o6e8c2a40k676387f90ee461b3@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=paolo.ciarrocchi@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).