git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: git@vger.kernel.org
Subject: RE: [FEATURE REQUEST] git clone, just clone selected branches?
Date: Thu, 11 Oct 2007 00:01:41 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710110000420.4174@racer.site> (raw)
In-Reply-To: <011d01c80b8e$b0c0dc30$04ac10ac@Jocke>

Hi,

On Thu, 11 Oct 2007, Joakim Tjernlund wrote:

> > -----Original Message-----
> > From: Johannes Schindelin [mailto:Johannes.Schindelin@gmx.de] 
> > 
> > thought it might be pretty easy for you to rewrite git-clone.sh to 
> > take advantage of git-fetch and git-remote, and that your desired 
> > feature would be easier to add then.  So easy that the whole thing 
> > would have taken you all of an hour or so.
> 
> Well, now I had to take a look and I think you are overestimating my 
> capabilities :) It is a 12KB script full of git-plumbing I have never 
> used, nor do I do sh scripts well. It might be an hour for you, but I 
> would probably have to spend the whole day :)

Heh.  git-clone is pretty crowded.  But it predates git-remote.  And I 
have a hunch that git-clone will be a trivial script when it calls 
git-remote and the git-fetch.

Ciao,
Dscho

  reply	other threads:[~2007-10-10 23:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 18:55 [FEATURE REQUEST] git clone, just clone selected branches? Joakim Tjernlund
2007-10-10 19:35 ` Johannes Schindelin
2007-10-10 21:25   ` Joakim Tjernlund
2007-10-10 21:56     ` Johannes Schindelin
2007-10-10 22:41       ` Joakim Tjernlund
2007-10-10 23:01         ` Johannes Schindelin [this message]
2007-10-10 19:38 ` Linus Torvalds
2007-10-10 21:36   ` Joakim Tjernlund
2007-10-11  9:18     ` Andreas Ericsson

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=Pine.LNX.4.64.0710110000420.4174@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=joakim.tjernlund@transmode.se \
    /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).