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 09:10:35 -0700 [thread overview]
Message-ID: <56b7f5510705190910h7e5ed03bnbc5a1b9a1369fc9f@mail.gmail.com> (raw)
In-Reply-To: <11795608922961-git-send-email-junkio@cox.net>
On 5/19/07, Junio C Hamano <junkio@cox.net> wrote:
> This teaches pack-objects to use .gitattributes mechanism so
> that the user can specify certain blobs are not worth spending
> CPU cycles to attempt deltification.
>
> The name of the attrbute is "delta", and when it is set to
> false, like this:
>
> == .gitattributes ==
> *.jpg -delta
>
> they are always stored in the plain-compressed base object
> representation.
And we could also have an attribute "repack" :
== .gitattributes ==
*.wmv -repack
which would result in *.wmv files [enormous] not being packed.
Since add_object_entry() now gets the name and
can reject objects (e.g. currently on their current packing status),
a call to "no_pack" which mirrors your new "no_try_delta"
could be inserted there. 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".
--
Dana L. How danahow@gmail.com +1 650 804 5991 cell
next prev parent reply other threads:[~2007-05-19 16:10 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 [this message]
2007-05-19 20:03 ` Junio C Hamano
2007-05-19 23:56 ` Dana How
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=56b7f5510705190910h7e5ed03bnbc5a1b9a1369fc9f@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).