From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [PATCH 0/2] remote-helpers: test fixes
Date: Mon, 20 May 2013 16:13:46 -0700 [thread overview]
Message-ID: <7v7gits0r9.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAMP44s0gK5EgD-pJb1NVrpJvYeyXmN_nS6MT7renFHhne1cZJg@mail.gmail.com> (Felipe Contreras's message of "Mon, 20 May 2013 17:53:34 -0500")
Felipe Contreras <felipe.contreras@gmail.com> writes:
> On Mon, May 20, 2013 at 5:47 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>
>>> Hi,
>>>
>>> I've setup a project in Travis CI for continuous integration with very good
>>> results, however, I had to apply a couple of fixes.
>>>
>>> I'm not sure if this is v1.8.3 material, but here they are.
>>
>> Thanks; I'll queue them at the tip of fc/remote-hg to graduate soon
>> after 1.8.3, then.
>
> No, they should be graduated first. The tip of fc/remote-hg is in pu,
> no? I have rebased that branch and squashed some fixes so every commit
> works on all versions of Mercurial. I will resend all the patches, the
> only reason I haven't done so is that I didn't want to create more
> noise before v1.8.3, and you said I was the one taking the decision
> when to merge remote-helper stuff to master.
Then is this v1.8.3 material? Please do not stay "I'm not sure" for
very long. I do not think we want -rc4 only for a contrib/ stuff.
For today's integration run I didn't want to wait so tentatively
they are queued at the tip of fc/remote-hg, and it is too late to
redo everything I did today, but I can requeue them for 'master' in
the tomorrow's cycle if you want.
next prev parent reply other threads:[~2013-05-20 23:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 21:10 [PATCH 0/2] remote-helpers: test fixes Felipe Contreras
2013-05-17 21:10 ` [PATCH 1/2] remote-helpers: tests: use python directly Felipe Contreras
2013-05-18 2:12 ` Junio C Hamano
2013-05-18 2:51 ` David Aguilar
2013-05-18 3:04 ` Felipe Contreras
2013-05-19 6:24 ` Junio C Hamano
2013-05-19 8:25 ` Felipe Contreras
2013-05-17 21:10 ` [PATCH 2/2] remote-hg: tests: fix hg merge Felipe Contreras
2013-05-20 22:47 ` [PATCH 0/2] remote-helpers: test fixes Junio C Hamano
2013-05-20 22:53 ` Felipe Contreras
2013-05-20 23:13 ` Junio C Hamano [this message]
2013-05-20 23:22 ` Felipe Contreras
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=7v7gits0r9.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--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 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).