git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Mark Levedahl <mdl123@verizon.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-unbundle - unbundle objects and references for disconnected transfer.
Date: Wed, 14 Feb 2007 16:03:00 -0500	[thread overview]
Message-ID: <20070214210300.GF28290@spearce.org> (raw)
In-Reply-To: <45D377A8.1080404@verizon.net>

Mark Levedahl <mdl123@verizon.net> wrote:
> Many of my uses of this result in 10-20 objects being transferred, so 
> I'm not sure keeping each pack is a real benefit. In particular, one use 
> is for daily updates between two sites via email where we tend to have a 
> lot of extra objects in the packs as we assume that not every bundle 
> actually gets applied, while the number of real new objects tends to be 
> small. On the other hand, given the manual nature of this operation, we 
> could always just follow up with repack -a -d, possibly guarded by a git 
> count. Thoughts?

I don't really have an opinion here, as I'm fortunate enough that
I can use an SSH or an anonymous git connection between all of my
repositories, and thus don't really have a need for bundle/unbundle.

Its just one of those operations which I thought would not happen
often, and when it did, probably would be big.  In which case keeping
the packfile would make the unbundle run faster, as you don't need
to create a huge mess of loose objects.

-- 
Shawn.

  reply	other threads:[~2007-02-14 21:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 14:10 Scripts to use "bundles" for moving data between repositories Mark Levedahl
2007-02-14 14:10 ` [PATCH] git-bundle - bundle objects and references for disconnected transfer Mark Levedahl
2007-02-14 14:10   ` [PATCH] git-unbundle - unbundle " Mark Levedahl
2007-02-14 14:10     ` [PATCH] Create a man page for git-bundle Mark Levedahl
2007-02-14 14:10       ` [PATCH] Create a man page for git-unbundle Mark Levedahl
2007-02-14 19:45     ` [PATCH] git-unbundle - unbundle objects and references for disconnected transfer Shawn O. Pearce
2007-02-14 20:57       ` Mark Levedahl
2007-02-14 21:03         ` Shawn O. Pearce [this message]
2007-02-14 22:43           ` Mark Levedahl
2007-02-14 21:18         ` Nicolas Pitre
2007-02-14 19:42   ` [PATCH] git-bundle - bundle " Shawn O. Pearce
2007-02-14 21:58   ` Johannes Schindelin
2007-02-14 23:19     ` Mark Levedahl
2007-02-14 23:55       ` Mark Levedahl
2007-02-15  0:15         ` Johannes Schindelin
2007-02-15  2:13           ` Mark Levedahl
2007-02-15 15:35             ` Johannes Schindelin
2007-02-15  0:07       ` Johannes Schindelin
2007-02-15  2:32         ` Mark Levedahl
2007-02-15 15:32           ` Johannes Schindelin
2007-02-16  0:12             ` Mark Levedahl
2007-02-16  0:40               ` Johannes Schindelin
2007-02-16  3:23                 ` Mark Levedahl
2007-02-14 14:13 ` Scripts to use "bundles" for moving data between repositories Matthieu Moy
2007-02-14 14:37   ` Mark Levedahl
2007-02-14 15:46 ` Johannes Schindelin
2007-02-14 17:11 ` Junio C Hamano
2007-02-14 17:56   ` Mark Levedahl
2007-02-14 18:00     ` Junio C Hamano
2007-02-14 21:24       ` Mark Levedahl
2007-02-14 21:26         ` Junio C Hamano
2007-02-14 18:20     ` 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=20070214210300.GF28290@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=mdl123@verizon.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).