public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Sep 2013, #02; Mon, 9)
Date: Tue, 10 Sep 2013 11:31:18 -0700	[thread overview]
Message-ID: <xmqqob80y1e1.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <vpqwqmpjdvk.fsf@anie.imag.fr> (Matthieu Moy's message of "Tue, 10 Sep 2013 10:10:39 +0200")

Matthieu Moy <Matthieu.Moy@grenoble-inp•fr> writes:

> Junio C Hamano <gitster@pobox•com> writes:
>
>> * mm/rebase-continue-freebsd-WB (2013-09-09) 1 commit
>>  - rebase: fix run_specific_rebase's use of "return" on FreeBSD
>>
>>  Work around a bug in FreeBSD shell that caused a regression to "git
>>  rebase" in v1.8.4.  It would be lovely to hear from FreeBSD folks a
>>  success report to make sure we didn't miss any other use of a bare
>>  "return" from dot-sourced script.
>>
>>  Will merge to 'next'.
>
> BTW, this is a candidate for maint too I guess.

Yes, thanks for reminding me.  I was planning to change that label
to "Will merge to 'master' and later to 'maint'" when it hits
'next'.

  reply	other threads:[~2013-09-10 18:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 22:53 What's cooking in git.git (Sep 2013, #02; Mon, 9) Junio C Hamano
2013-09-10  8:10 ` Matthieu Moy
2013-09-10 18:31   ` Junio C Hamano [this message]
2013-09-10 16:27 ` Jens Lehmann
2013-09-10 18:31   ` Junio C Hamano
2013-09-11 19:07   ` [PATCH] Improve documentation concerning the status.submodulesummary setting Jens Lehmann
2013-09-11 19:58     ` Matthieu Moy
2013-09-20 22:29   ` What's cooking in git.git (Sep 2013, #02; Mon, 9) Junio C Hamano
2013-09-22 13:00     ` Jens Lehmann
2013-09-22 17:06       ` Matthieu Moy
2013-09-11 21:33 ` Stefan Beller

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=xmqqob80y1e1.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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