git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dana How" <danahow@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org, danahow@gmail.com
Subject: Re: [PATCH 2/2] Teach "delta" attribute to pack-objects.
Date: Sat, 19 May 2007 16:56:23 -0700	[thread overview]
Message-ID: <56b7f5510705191656y1a5cdb1cn1b8b1082519f4bc3@mail.gmail.com> (raw)
In-Reply-To: <7v4pm8wpgc.fsf@assigned-by-dhcp.cox.net>

On 5/19/07, Junio C Hamano <junkio@cox.net> wrote:
> "Dana How" <danahow@gmail.com> writes:
> > ...  But such an attribute should be
> > ignored when --stdout is in effect -- it only affects on-disk
> > repacking, not packing for transfers, which is why it's named "repack".
>
> Yes -- if we want to have an option to keep objects selectively
> left out of packs in loose format, you would need 'repack' which
> acts differently between the server-feeding-client case vs
> packing-repository case.
>
> Which is a bigger change that I did not want to show in the
> quick-and-clean patch, but I would agree we would want both.

OK -- I'll put this on the back-burner with the so-called
"ent:relative" patch and I'll revisit this once your "delta"
attribute shows up in next or master.

At the moment I'm experimenting on a git repository with
a 4.5GB checkout,  and 18 months of history in 4K commits
comprising 100GB (uncompressed) of blobs stored in
7 packfiles of 2GB or less.  Hopefully I'll be able to say
more about tweaking packing shortly.

Thanks,
-- 
Dana L. How  danahow@gmail.com  +1 650 804 5991 cell

  reply	other threads:[~2007-05-19 23:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19  7:48 [PATCH 1/2] pack-objects: pass fullname down to add_object_entry() Junio C Hamano
2007-05-19  7:48 ` [PATCH 2/2] Teach "delta" attribute to pack-objects Junio C Hamano
2007-05-19 16:10   ` Dana How
2007-05-19 20:03     ` Junio C Hamano
2007-05-19 23:56       ` Dana How [this message]
2007-05-22 16:04   ` Nicolas Pitre

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=56b7f5510705191656y1a5cdb1cn1b8b1082519f4bc3@mail.gmail.com \
    --to=danahow@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).