From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2008, #09; Sun, 31)
Date: Mon, 1 Sep 2008 15:16:23 +0700 [thread overview]
Message-ID: <fcaeb9bf0809010116p68a638dck4f8e31d49e51c3fb@mail.gmail.com> (raw)
In-Reply-To: <7vd4jo1jc6.fsf@gitster.siamese.dyndns.org>
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?
--
Duy
next prev parent reply other threads:[~2008-09-01 8:17 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 [this message]
2008-09-01 19:33 ` 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=fcaeb9bf0809010116p68a638dck4f8e31d49e51c3fb@mail.gmail.com \
--to=pclouds@gmail.com \
--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).