Git development
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] should these two topics graduate to 'master' soon?
Date: Wed, 29 Mar 2017 07:55:01 -0500	[thread overview]
Message-ID: <E1ctD7t-00015R-9G@mylo.jdl.com> (raw)
In-Reply-To: <xmqqshlxckr2.fsf@gitster.mtv.corp.google.com>

So, like, Junio C Hamano said:
> There are two topics that are marked as "Will cook in 'next'" for
> practically forever in the "What's cooking" reports.  The world may
> have become ready for one or both of them, in which case we should
> do the merge not too late in the cycle.
> 
> * jc/merge-drop-old-syntax (2015-04-29) 1 commit
> 
> 
> * jk/no-looking-at-dotgit-outside-repo-final (2016-10-26) 1 commit
> 
> Opinions?

While I have no technical data on these issues, I think
they should go in.

jdl

      parent reply	other threads:[~2017-03-29 12:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 18:35 [RFC] should these two topics graduate to 'master' soon? Junio C Hamano
2017-03-28 18:51 ` Jonathan Nieder
2017-03-28 19:19   ` Jeff King
2017-03-30 19:18     ` Junio C Hamano
2017-03-28 18:57 ` Stefan Beller
2017-03-29 12:55 ` Jon Loeliger [this message]

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=E1ctD7t-00015R-9G@mylo.jdl.com \
    --to=jdl@jdl.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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