git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Joey Hess <id@joeyh.name>
Cc: "Git Mailing List" <git@vger.kernel.org>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
	"Peter Simons" <simons@cryp.to>
Subject: Re: reversion in GIT_COMMON_DIR refs path
Date: Tue, 16 May 2017 19:50:27 +0200	[thread overview]
Message-ID: <CACBZZX5AgdMTceBAVftNp0goHpf2-hqx8GzvJshx2n1FtCGsBw@mail.gmail.com> (raw)
In-Reply-To: <20170516171028.5eagqr2sw5a2i77d@kitenet.net>

On Tue, May 16, 2017 at 7:10 PM, Joey Hess <id@joeyh.name> wrote:
> Bisecting this test suite failure
> https://git-annex.branchable.com/git-annex_in_nixpkgs_fails_with_git-2.13.0/
> I landed on commit f57f37e2e1bf11ab4cdfd221ad47e961ba9353a0 to git.

That links's broken for me. Looking at your wiki it looks like you
mean: https://git-annex.branchable.com/bugs/git-annex_in_nixpkgs_fails_with_git-2.13.0/

I have no idea what this bug is about, but side-question: It looks
like this is git-annex's own test suite that's failing with 2.13.0, is
that right?

It would be very nice to have a test in git itself to test with
git-annex. I.e. some optional test that just pulls down the latest
git-annex release & runs its tests against the git we're building.

Thanks for annex b.t.w., I use it a lot.

  reply	other threads:[~2017-05-16 17:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 17:10 reversion in GIT_COMMON_DIR refs path Joey Hess
2017-05-16 17:50 ` Ævar Arnfjörð Bjarmason [this message]
2017-05-16 17:59   ` Joey Hess
2017-05-16 20:37     ` [PATCH] tests: add an optional test to test git-annex Ævar Arnfjörð Bjarmason
2017-05-16 22:10       ` Joey Hess
2017-05-17  2:45       ` Junio C Hamano
2017-05-17  6:47         ` Ævar Arnfjörð Bjarmason
2017-05-17 10:19           ` Junio C Hamano
2017-05-17 19:33             ` Ævar Arnfjörð Bjarmason
2017-05-17 23:03               ` Stefan Beller
2017-05-17 23:59                 ` Brandon Williams
2017-05-17 23:56             ` Brandon Williams
2017-05-19 14:37 ` reversion in GIT_COMMON_DIR refs path Joey Hess
2017-05-22 11:11   ` Duy Nguyen

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=CACBZZX5AgdMTceBAVftNp0goHpf2-hqx8GzvJshx2n1FtCGsBw@mail.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=id@joeyh.name \
    --cc=pclouds@gmail.com \
    --cc=simons@cryp.to \
    /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).