From: "Henrik Grubbström (Grubba)" <grubba@grubba.org>
To: git@vger.kernel.org
Cc: "Henrik Grubbström " <grubba@grubba.org>
Subject: [PATCH RFC v2 0/4] Patches to avoid reporting conversion changes.
Date: Sun, 25 Apr 2010 18:29:04 +0200 [thread overview]
Message-ID: <cover.1272210580.git.grubba@grubba.org> (raw)
This is the second go at having the git index keep track of the
conversion mode and corresponding normalized blob sha1 for files.
Since last time the diff behaviour patch has been removed, and
with it the need for storing of the normalized blob and thus
the gc patch. Some basic test cases have been added.
Thanks to Junio C Hamano for the suggestion and some of the tests.
Henrik Grubbström (Grubba) (4):
sha1_file: Added index_blob().
cache: Added ce_norm_sha1() and related cache_entry fields.
cache: Added index extension "NORM".
t/t0021: Test that conversion changes are detected.
cache.h | 22 ++++++++++++++++
convert.c | 31 +++++++++++++++++++++++
read-cache.c | 66 +++++++++++++++++++++++++++++++++++++++++++------
sha1_file.c | 19 ++++++++++++++
t/t0021-conversion.sh | 50 +++++++++++++++++++++++++++++++++++++
5 files changed, 180 insertions(+), 8 deletions(-)
next reply other threads:[~2010-04-25 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 16:29 Henrik Grubbström (Grubba) [this message]
2010-04-25 16:29 ` [PATCH RFC v2 1/4] sha1_file: Added index_blob() Henrik Grubbström (Grubba)
2010-04-25 16:29 ` [PATCH RFC v2 2/4] cache: Added ce_norm_sha1() and related cache_entry fields Henrik Grubbström (Grubba)
2010-04-25 16:29 ` [PATCH RFC v2 3/4] cache: Added index extension "NORM" Henrik Grubbström (Grubba)
2010-04-25 16:29 ` [PATCH RFC v2 4/4] t/t0021: Test that conversion changes are detected Henrik Grubbström (Grubba)
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=cover.1272210580.git.grubba@grubba.org \
--to=grubba@grubba.org \
--cc=git@vger.kernel.org \
/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).