From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC/PATCH] t7011: Mark fixed test as such
Date: Sun, 29 Nov 2009 15:47:35 +0700 [thread overview]
Message-ID: <fcaeb9bf0911290047t43ea3040x730e04baa81d8a98@mail.gmail.com> (raw)
In-Reply-To: <0327ed3d7c4621f205d2d111254d716bd1b06c28.1259432535.git.git@drmicha.warpmail.net>
On 11/29/09, Michael J Gruber <git@drmicha.warpmail.net> wrote:
> Test 16/17 had been fixed since its introduction in b4d1690 (Teach Git
> to respect skip-worktree bit (reading part), 2009-08-20). So, mark it as
> expect_success rather than expect_failure.
>
> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
No ACK. See below.
> ---
> I'm actually wondering about 17/17 as well.
> If commit is called with a file name then shouldn't it simply commit the
> current state of the file in the worktree, no matter what the index or
> skip-worktree say? I therefore think 17/17 should be expect_success
> and have no test_must_fail.
Both 16/17 and 17/17 ensure that Git won't look at files on worktree
if they are marked as skip-worktree (by definition of skip-worktree,
you can safely ignore worktree, otherwise you would not mark them as
such). 16/17 happens to pass, not because it does not touch worktree,
but because the base index does not have "1", which happens to is the
same situation in 16/17 (test commit when "1" is gone). The result is
OK but it is actually not (17/17 shows this clearer as it commits the
worktree version).
--
Duy
next prev parent reply other threads:[~2009-11-29 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 18:24 [RFC/PATCH] t7011: Mark fixed test as such Michael J Gruber
2009-11-29 8:47 ` Nguyen Thai Ngoc Duy [this message]
2009-11-29 13:57 ` Michael J Gruber
2009-11-30 1:56 ` Nguyen Thai Ngoc Duy
2009-11-30 12:49 ` Michael J Gruber
2009-11-30 13:18 ` Nguyen Thai Ngoc Duy
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=fcaeb9bf0911290047t43ea3040x730e04baa81d8a98@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@drmicha.warpmail.net \
--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 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).