git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Pickens <jepicken@gmail.com>
To: Git ML <git@vger.kernel.org>
Cc: Jeff King <peff@peff.net>, Jakub Narebski <jnareb@gmail.com>
Subject: Re: 'git clone' doesn't use alternates automatically?
Date: Sat, 31 Jan 2009 14:43:13 -0700	[thread overview]
Message-ID: <885649360901311343r2a9bd1b5l5f8226218000dbe8@mail.gmail.com> (raw)
In-Reply-To: <m3tz7fw5ek.fsf@localhost.localdomain>

On Sat, Jan 31, 2009 at 2:08 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> James Pickens <jepicken@gmail.com> writes:
>
>> So, is there any reason 'git clone' shouldn't automatically use
>> the alternates that it copied into the new repository?  I might
>> look into writing a patch if nobody objects.
>
> Alternates are fragile with respect to garbage collecting in the
> repository you borrow objects from.

I think that's irrelevant in this case.  The scenario is that I
clone repo A, which is borrowing objects from repo B.  So repo A
was already assuming that it's safe to borrow from B.

The current behavior is that the clone of A also borrows from B
automatically.  What I am asking is whether 'git clone' should
take advantage of that to avoid copying redundant objects from A
into the clone.  They will get deleted the first time I run 'git
gc' in the clone anyways.

James

  reply	other threads:[~2009-01-31 21:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 22:12 'git clone' doesn't use alternates automatically? James Pickens
2009-01-31  7:12 ` Jeff King
2009-01-31 20:08   ` James Pickens
2009-01-31 21:08     ` Jakub Narebski
2009-01-31 21:43       ` James Pickens [this message]
2009-01-31 21:55     ` Jeff King
2009-02-01  1:19       ` Junio C Hamano
2009-02-02 13:07         ` Jeff King
2009-02-03  4:30           ` Junio C Hamano
2009-02-03  6:06             ` Jeff King
2009-02-01  0:55     ` Junio C Hamano
2009-02-01  1:32       ` James Pickens
2009-02-01  1:38         ` Junio C Hamano

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=885649360901311343r2a9bd1b5l5f8226218000dbe8@mail.gmail.com \
    --to=jepicken@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=peff@peff.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;
as well as URLs for NNTP newsgroup(s).