Jeff King writes:
> On Tue, Mar 28, 2017 at 11:51:49AM -0700, Jonathan Nieder wrote:
>
>> > * jc/merge-drop-old-syntax (2015-04-29) 1 commit
>> >
>> > This topic stops "git merge HEAD " syntax that
>> > has been deprecated since October 2007 (and we have issued a
>> >
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.
>
> *
On Tue, Mar 28, 2017 at 11:51:49AM -0700, Jonathan Nieder wrote:
> > * jc/merge-drop-old-syntax (2015-04-29) 1 commit
> >
> > This topic stops "git merge HEAD " syntax that
> > has been deprecated since October 2007 (and we have issued a
> > warning message since around v2.5.0 when the
On Tue, Mar 28, 2017 at 11:35 AM, Junio C Hamano wrote:
> 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
Hi Junio,
Junio C Hamano wrote:
> 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.
>
> *
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
This
6 matches
Mail list logo