From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] add --remote option to git-clone.
Date: Thu, 1 Feb 2007 17:06:57 -0500 [thread overview]
Message-ID: <20070201220657.GB19271@fieldses.org> (raw)
In-Reply-To: <20070201220122.GF17617@mellanox.co.il>
On Fri, Feb 02, 2007 at 12:01:22AM +0200, Michael S. Tsirkin wrote:
> I'm often annoyed by the fact that when I clone from this repository,
> I get a copy of all topic branches and origin tracking master
> by default, when I actually might only want to work on a different
> topic. And getting all extra branches is annoying on a slow connection.
Can you quantify "annoying"?
Not a challenge, I'm just curious--I would've thought that, for most
projects, even with long-lived topic branches, it wouldn't be that
expensive to get a second branch once you'd gotten one.
--b.
next prev parent reply other threads:[~2007-02-01 22:07 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 [this message]
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
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=20070201220657.GB19271@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=mst@mellanox.co.il \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.