From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org, Max Horn <max@quendi.de>
Subject: Re: What's cooking in git.git (Mar 2014, #04; Thu, 20)
Date: Fri, 21 Mar 2014 14:33:32 -0700 [thread overview]
Message-ID: <xmqqpplfs0cz.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqq38ibtgj1.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Fri, 21 Mar 2014 13:58:58 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Torsten Bögershausen <tboegi@web.de> writes:
>
>> On 03/20/2014 10:09 PM, Junio C Hamano wrote:
>>> * ap/remote-hg-skip-null-bookmarks (2014-03-19) 1 commit
>>> - remote-hg: do not fail on invalid bookmarks
>>>
>>> Will merge to 'next'.
>> Hmm, am I the only one who has 11 failures in test-hg-hg-git.sh,
>> like this:
>> (Tested under Debian 7, commit 04570b241ddb53ad2f355977bae541bd7ff32af5)
>>
>>
>>
>> master cde5672] clear executable bit
>> Author: A U Thor <author@example.com>
>> 1 file changed, 0 insertions(+), 0 deletions(-)
>> mode change 100755 => 100644 alpha
>> WARNING: Ignoring invalid bookmark 'master'
>> To hg::../hgrepo-git
>> ! [remote rejected] master -> master
>> error: failed to push some refs to 'hg::../hgrepo-git'
>> not ok 1 - executable bit
>> []
>> # failed 11 among 11 test(s)
>> 1..11
>
> This has again been replaced; I'll queue it as d06f17f8 (remote-hg:
> do not fail on invalid bookmarks, 2014-03-21) on 'pu'.
>
> Please holler if this still breaks for you.
>
> Thanks.
Ah, you seem to have sent a good review on that patch while I was
looking at other topics ;-) And they all make sense, I think.
Thanks.
next prev parent reply other threads:[~2014-03-21 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 21:09 What's cooking in git.git (Mar 2014, #04; Thu, 20) Junio C Hamano
2014-03-20 22:03 ` Torsten Bögershausen
2014-03-20 22:36 ` Junio C Hamano
2014-03-21 20:58 ` Junio C Hamano
2014-03-21 21:33 ` Junio C Hamano [this message]
2014-03-20 22:31 ` Junio C Hamano
2014-03-21 17:20 ` kirr
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=xmqqpplfs0cz.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=max@quendi.de \
--cc=tboegi@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.