git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2008, #09; Sun, 31)
Date: Mon, 01 Sep 2008 12:33:48 -0700	[thread overview]
Message-ID: <7vprnnvexv.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: fcaeb9bf0809010116p68a638dck4f8e31d49e51c3fb@mail.gmail.com

"Nguyen Thai Ngoc Duy" <pclouds@gmail.com> writes:

> On 9/1/08, Junio C Hamano <gitster@pobox.com> wrote:
>>  * nd/worktree (Sat Aug 30 16:15:32 2008 +0700) 5 commits
>>   - setup_git_directory(): fix move to worktree toplevel directory
>>   - update-index: fix worktree setup
>>   + read-tree: setup worktree if merge is required
>>   + grep: fix worktree setup
>>   + diff*: fix worktree setup
>>
>>  The last two fail test suite.
>
> "make test" on pu did not fail on my machine. What tests failed?

*** t1006-read-tree-m-i.sh ***
* FAIL 1: setup
	
	
		mkdir it.git &&
		(
			GIT_DIR=. &&
			export GIT_DIR &&
			cd it.git &&
			git init &&
			M="1 2 3 4 5 6 7 8" &&
			for i in $M 9; do echo $i; done >file &&
			cat file >elif &&
			git update-index --add file elif &&
		...

which is part of my private test suite.

While it is a change in behaviour, after looking at what the test does
again, I do not think this use case is worth supporting.

      reply	other threads:[~2008-09-01 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01  6:16 What's cooking in git.git (Aug 2008, #09; Sun, 31) Junio C Hamano
2008-09-01  8:16 ` Nguyen Thai Ngoc Duy
2008-09-01 19:33   ` Junio C Hamano [this message]

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=7vprnnvexv.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.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).