From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Stefan Beller <sbeller@google.com>,
Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Oct 2016, #06; Mon, 24)
Date: Thu, 27 Oct 2016 17:47:12 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610271746450.3264@virtualbox> (raw)
In-Reply-To: <23f15627-4964-7ba9-45c3-899366d621bd@kdbg.org>
Hi Hannes,
On Tue, 25 Oct 2016, Johannes Sixt wrote:
> Am 25.10.2016 um 20:13 schrieb Stefan Beller:
> > On Tue, Oct 25, 2016 at 10:15 AM, Junio C Hamano <gitster@pobox.com> wrote:
> > > - the "off-by-one fix" part of sb/submodule-ignore-trailing-slash
> > > needs to be in the upcoming release but the "trailing /. in base
> > > should not affect the resolution of ../relative/path" part that
> > > is still under discussion can wait. Which means we'd need a few
> > > more !MINGW prerequisites in the tests by -rc0.
> > >[...]
> >
> > So maybe instead of adding !MINGW we rather want to apply
> > https://public-inbox.org/git/2908451e-4273-8826-8989-5572263cc283@kdbg.org/
> > instead for now?
>
> I was about to submit this very patch again, and only then saw your message.
> So, yes, that's what I propose, too.
>
> Dscho, does this patch fix the test failures that you observed, too?
> Unfortunately, it goes against our endeavor to reduce subshells.
I am fine with the patch, even if I did not have a chance to test it yet
(ran out of time today).
Ciao,
Dscho
next prev parent reply other threads:[~2016-10-27 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 1:09 What's cooking in git.git (Oct 2016, #06; Mon, 24) Junio C Hamano
2016-10-25 2:27 ` Stefan Beller
2016-10-25 17:15 ` Junio C Hamano
2016-10-25 18:13 ` Stefan Beller
2016-10-25 18:34 ` Junio C Hamano
2016-10-25 21:24 ` Johannes Sixt
2016-10-27 15:47 ` Johannes Schindelin [this message]
2016-10-25 18:30 ` Jeff King
2016-10-25 18:41 ` 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=alpine.DEB.2.20.1610271746450.3264@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=sbeller@google.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).