From: "Michael S. Tsirkin" <mst@mellanox.co.il>
To: Junio C Hamano <junkio@cox.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] add --remote option to git-clone.
Date: Mon, 5 Feb 2007 20:48:14 +0200 [thread overview]
Message-ID: <20070205184814.GD15775@mellanox.co.il> (raw)
In-Reply-To: <7vmz3smqpp.fsf@assigned-by-dhcp.cox.net>
> Junio C Hamano <junkio@cox.net> writes:
> > Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> > git clone git://.../git.git#html
> >
> > to mean "just fetch the branch html, and check it out".
>
> Except that I do not particularly think the URL fragment
> notation is such a "cool" syntax.
OK, but I think it would be very good I think to have *some* URL-like syntax for
git-fetch etc - people are used to copying URLs out of mail (lots of MUAs even
highlight these nicely) so I often see that current syntax <URL> <branch> confuses
people: they seem to lose the branch and fetch/pull the wrong one.
--
MST
prev parent reply other threads:[~2007-02-05 18:47 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
2007-02-05 18:48 ` Michael S. Tsirkin [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=20070205184814.GD15775@mellanox.co.il \
--to=mst@mellanox.co.il \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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