From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org, Alexandre Julliard <julliard@winehq.org>
Subject: Re: [PATCH] Write index file on any checkout of files
Date: Thu, 28 Feb 2008 12:25:16 -0800 [thread overview]
Message-ID: <7vfxvcj0b7.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0802281058190.19665@iabervon.org> (Daniel Barkalow's message of "Thu, 28 Feb 2008 10:58:59 -0500 (EST)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> We need to rewrite the index file when we check out files, even if we
> haven't modified the blob info by reading from another tree, so that
> we get the stat cache to include the fact that we just modified the
> file so it doesn't need to be refreshed.
Thanks, Alexandre, for spotting.
> -static int checkout_paths(const char **pathspec)
> +static int checkout_paths(const char **pathspec, int newfd, struct lock_file *lock_file)
> {
> ...
> @@ -554,11 +549,14 @@ int cmd_checkout(int argc, const char **argv, const char *prefix)
> }
> }
>
> + int newfd;
> + struct lock_file *lock_file = xcalloc(1, sizeof(struct lock_file));
> + newfd = hold_locked_index(lock_file, 1);
> + read_cache();
> +
> if (source_tree)
> read_tree_some(source_tree, pathspec);
> - else
> - read_cache();
> - return checkout_paths(pathspec);
> + return checkout_paths(pathspec, newfd, lock_file);
Aside from decl-after-statement, I suspect that at this point
these all should go to checkout_paths() function itself, that
takes pathspec and source_tree (which could be NULL), but that
is only "logical code organization" issue. Thanks for fixing.
I however would have liked if this were caught while the topic
was still cooking in 'next'.
There was a process failure somewhere, which makes me worry more
than just this single bug that escaped to 'master'. Alex
Riesen's segv fix in another thread makes it double X-<.
next prev parent reply other threads:[~2008-02-28 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 14:11 git-checkout regression? Alexandre Julliard
2008-02-28 15:11 ` Daniel Barkalow
2008-02-28 15:58 ` [PATCH] Write index file on any checkout of files Daniel Barkalow
2008-02-28 16:07 ` Alexandre Julliard
2008-02-28 16:11 ` Daniel Barkalow
2008-02-28 20:25 ` Junio C Hamano [this message]
2008-02-28 21:21 ` Daniel Barkalow
2008-02-28 21:44 ` Junio C Hamano
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=7vfxvcj0b7.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=julliard@winehq.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.