From: "Shawn O. Pearce" <spearce@spearce.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <junkio@cox.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org, "Michael S. Tsirkin" <mst@mellanox.co.il>
Subject: Re: [PATCH] add --remote option to git-clone.
Date: Mon, 5 Feb 2007 14:34:29 -0500 [thread overview]
Message-ID: <20070205193429.GA8409@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702051014040.8424@woody.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> I realize that the
>
> git clone <repo> [<dir>]
>
> means that we can't have the same syntax as "git pull" (which doesn't take
> the <dir> part), but that doesn't make the "#branch" syntax any better.
>
> So I much prefer the
>
> git clone [--default branch] [--branch x]* <repo> [<dir>]
>
> kind of syntax.
Ugh. That means the bash completion cannot (easily) do something
fancy, like tab completion of branch names within <repo>. Yea,
its not fast on slow links, but it beats typing out an ugly branch
name. :-)
--
Shawn.
next prev parent reply other threads:[~2007-02-05 19:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 22:01 [PATCH] add --remote option to git-clone Michael S. Tsirkin
2007-02-01 22:06 ` J. Bruce Fields
2007-02-01 22:14 ` Shawn O. Pearce
2007-02-01 23:01 ` Michael S. Tsirkin
2007-02-01 23:42 ` Yann Dirson
2007-02-01 23:29 ` Johannes Schindelin
2007-02-01 23:31 ` Shawn O. Pearce
2007-02-01 23:47 ` Michael S. Tsirkin
2007-02-01 23:53 ` Johannes Schindelin
2007-02-02 1:25 ` Junio C Hamano
2007-02-02 10:48 ` Johannes Schindelin
2007-02-03 3:00 ` Junio C Hamano
2007-02-03 9:06 ` Jakub Narebski
2007-02-03 9:27 ` Junio C Hamano
2007-02-05 11:51 ` Johannes Schindelin
2007-02-05 17:58 ` Junio C Hamano
2007-02-05 18:43 ` Linus Torvalds
2007-02-05 18:55 ` Michael S. Tsirkin
2007-02-05 19:34 ` Shawn O. Pearce [this message]
2007-02-05 18:48 ` Michael S. Tsirkin
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=20070205193429.GA8409@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=mst@mellanox.co.il \
--cc=torvalds@linux-foundation.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