Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 4/9] Discard "deleted" cache entries after using them to update the working tree
Date: Fri, 25 Jan 2008 15:53:35 -0800	[thread overview]
Message-ID: <7v63xh5uo0.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0801251820330.13593@iabervon.org> (Daniel Barkalow's message of "Fri, 25 Jan 2008 18:24:52 -0500 (EST)")

Daniel Barkalow <barkalow@iabervon.org> writes:

> It's likely that this should get merged in some way with Linus's series to 
> handle the in-core index differently in general. But this is a simple 
> solution to the problem that's sufficient for this particular series.

Just to let you know, the early parts of lt/in-core-index series
are already in 'next', and it will be one of the first topics to
graduate to 'master' post 1.5.4.

I think we both understand that this round is sent purely for
discussion and I won't be picking them up right now nor later
before the "for possible inclusion" resend you will be making
post 1.5.4, so it should not matter too much which exact version
this round is based on.

It however may be worthwhile for you to plan rebasing your
future rounds on top of 077c48df8a72b046a2f562fedffa1c3d3a73a4e2
(read-cache.c: fix a couple more CE_REMOVE conversion).

Thanks.

  reply	other threads:[~2008-01-25 23:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 23:24 [PATCH 4/9] Discard "deleted" cache entries after using them to update the working tree Daniel Barkalow
2008-01-25 23:53 ` Junio C Hamano [this message]
2008-01-26  0:54   ` Daniel Barkalow
  -- strict thread matches above, loose matches on Subject: below --
2008-02-04 18:35 Daniel Barkalow
2008-02-05  1:25 ` Johannes Schindelin
2008-02-05 20:38   ` Daniel Barkalow

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=7v63xh5uo0.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.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