git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gummerer <t.gummerer@gmail.com>
To: git@vger.kernel.org
Cc: trast@student.ethz.ch, pclouds@gmail.com, mhagger@alum.mit.edu,
	gitster@pobox.com, robin.rosenberg@dewire.com,
	t.gummerer@gmail.com
Subject: [PATCH/RFC v4 0/13] Introduce index file format version 5
Date: Thu, 16 Aug 2012 11:58:36 +0200	[thread overview]
Message-ID: <1345111129-6925-1-git-send-email-t.gummerer@gmail.com> (raw)

Previous rounds of the series are at $gmane/202752 and $gmane/202923
and $gmane/203088.

The modification to t3700 was removed as the smudge marker is replaced
with a CE_SMUDGED flag and therefore the code doesn't interfere with
the test.

Changes since the last round:

 [PATCH/RFC v4 01/13] Move index v2 specific functions to their own
 [PATCH/RFC v4 02/13] read-cache.c: Re-read index if index file
    Re-read the index file if the index file has changed since
    the first time we read it.  Checking if the index file changed
    is done by using it's stat data.

 [PATCH/RFC v4 03/13] t2104: Don't fail for index versions other than
 [PATCH/RFC v4 04/13] Add documentation of the index-v5 file format
    Documentation updates as suggested by Junio.

 [PATCH/RFC v4 05/13] Make in-memory format aware of stat_crc
 [PATCH/RFC v4 06/13] Read index-v5
    Replace the pointer casts with ptr_add makro as suggested by Junio.

    Use a CE_SMUDGED flag instaed of ce_mtime as smudge marker.

    Ignore the crc sum if we don't trust_cetime, since it may give
    us wrong results.

 [PATCH/RFC v4 07/13] Read resolve-undo data
    No longer do the conversion in resolve-undo.c but in
    read-cache-v5.c.  (The same is valid for 11/13)

 [PATCH/RFC v4 08/13] Read cache-tree in index-v5
    No longer do the conversion in cache-tree.c but in
    read-cache-v5.c.  (The same is valid for 10/13)

 [PATCH/RFC v4 09/13] Write index-v5
 [PATCH/RFC v4 10/13] Write index-v5 cache-tree data
 [PATCH/RFC v4 11/13] Write resolve-undo data for index-v5
 [PATCH/RFC v4 12/13] update-index.c: rewrite index when
    Don't introduce the force-rewrite option, but always rewrite the
    index if a index-version is given.

 [PATCH/RFC v4 13/13] p0002-index.sh: add perf test for the index

             reply	other threads:[~2012-08-16  9:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  9:58 Thomas Gummerer [this message]
2012-08-16  9:58 ` [PATCH/RFC v4 01/13] Move index v2 specific functions to their own file Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 02/13] read-cache.c: Re-read index if index file changed Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 03/13] t2104: Don't fail for index versions other than [23] Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 04/13] Add documentation of the index-v5 file format Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 05/13] Make in-memory format aware of stat_crc Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 06/13] Read index-v5 Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 07/13] Read resolve-undo data Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 08/13] Read cache-tree in index-v5 Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 09/13] Write index-v5 Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 10/13] Write index-v5 cache-tree data Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 11/13] Write resolve-undo data for index-v5 Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 12/13] update-index.c: rewrite index when index-version is given Thomas Gummerer
2012-08-16  9:58 ` [PATCH/RFC v4 13/13] p0002-index.sh: add perf test for the index formats Thomas Gummerer

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=1345111129-6925-1-git-send-email-t.gummerer@gmail.com \
    --to=t.gummerer@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mhagger@alum.mit.edu \
    --cc=pclouds@gmail.com \
    --cc=robin.rosenberg@dewire.com \
    --cc=trast@student.ethz.ch \
    /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).