git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: git@vger.kernel.org, tboegi@web.de, mhagger@alum.mit.edu,
	mlevedahl@gmail.com, Jeff King <peff@peff.net>,
	Johannes Sixt <j6t@kdbg.org>
Subject: Re: What's cooking in git.git (Jul 2013, #09; Mon, 29)
Date: Wed, 31 Jul 2013 11:51:55 -0700	[thread overview]
Message-ID: <7v4nbav9ys.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <51F94DFD.5020101@ramsay1.demon.co.uk> (Ramsay Jones's message of "Wed, 31 Jul 2013 18:48:45 +0100")

Ramsay Jones <ramsay@ramsay1.demon.co.uk> writes:

>>  I am personally in favor of this simpler solution.  Comments?
>
> I had expected this to me marked for 'master'.
>
> Has this simply been overlooked, or do you have reservations about
> applying this patch?

I am just being careful and do want to keep it cooking in 'next'
during the feature freeze.  The more users work with 'next' (not
"work *on* 'next'"), the more confidence we would be with, and
hopefully this can be one of the topis that graduate early after
the 1.8.4 release.

  reply	other threads:[~2013-07-31 18:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 22:43 What's cooking in git.git (Jul 2013, #09; Mon, 29) Junio C Hamano
2013-07-31 17:48 ` Ramsay Jones
2013-07-31 18:51   ` Junio C Hamano [this message]
2013-08-01 20:51     ` Ramsay Jones
2013-08-01 21:12       ` Junio C Hamano
2013-08-03 13:37         ` Mark Levedahl
2013-08-05 16:29           ` Junio C Hamano
2013-08-03  6:50       ` Torsten Bögershausen
2013-08-03  7:04         ` Torsten Bögershausen

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=7v4nbav9ys.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    --cc=mhagger@alum.mit.edu \
    --cc=mlevedahl@gmail.com \
    --cc=peff@peff.net \
    --cc=ramsay@ramsay1.demon.co.uk \
    --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).