From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [WIP PATCH] Teach read-tree the -n|--dry-run option
Date: Tue, 17 May 2011 23:15:14 +0200 [thread overview]
Message-ID: <4DD2E562.90605@web.de> (raw)
In-Reply-To: <4DD2CFD4.7060508@web.de>
Am 17.05.2011 21:43, schrieb Jens Lehmann:
> The only exceptions where I could not make that replacement without
> breaking a test were:
>
> * t1001:381 (#25) new file conflicts with untracked directory
> This should have been detected by verify_absent_1(), but that function
> is left early when opts->update is 0. Will look into that.
>
> * 1011:95 (#5) read-tree with empty .git/info/sparse-checkout
> * t1011:163 (#11) read-tree updates worktree, dirty case
> Not sure about those two as I haven't got much experience with sparse
> checkout. Will dig further, pointers welcome.
I found the reason for all three failures, patch coming.
next prev parent reply other threads:[~2011-05-17 21:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 20:03 What's cooking in git.git (May 2011, #06; Fri, 13) Junio C Hamano
2011-05-14 3:03 ` Nguyen Thai Ngoc Duy
2011-05-14 17:37 ` Junio C Hamano
2011-05-15 4:51 ` Nguyen Thai Ngoc Duy
2011-05-15 16:50 ` Jens Lehmann
2011-05-15 20:23 ` Junio C Hamano
2011-05-17 19:43 ` [WIP PATCH] Teach read-tree the -n|--dry-run option Jens Lehmann
2011-05-17 21:15 ` Jens Lehmann [this message]
2011-05-17 22:47 ` Junio C Hamano
2011-05-19 17:47 ` [RFC PATCH] unpack-trees: add check_worktree flag to enable dry-run functionality Jens Lehmann
2011-05-19 18:14 ` Junio C Hamano
2011-05-19 18:21 ` Jens Lehmann
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=4DD2E562.90605@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.