git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: What's cooking in git.git (Jan 2019, #03; Fri, 18)
Date: Sat, 19 Jan 2019 09:50:46 -0800	[thread overview]
Message-ID: <xmqqwon0h6yx.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CABPp-BFmYoeiOaB9Pf70TC3XftXjMEHGrPqxS8TgiiXR39q2rQ@mail.gmail.com> (Elijah Newren's message of "Fri, 18 Jan 2019 17:13:08 -0800")

Elijah Newren <newren@gmail.com> writes:

>>  On hold.
>>  cf. <CABPp-BFckuONYcGGkCY3BuPypRULmhsk_OFHyYA2E4jM66BfeQ@mail.gmail.com>
>
> Is the "on hold" comment still accurate?

Not anymore.  Back when I wrote it it was unclear to me what the
best way forward was (e.g. should one become dependent on the other
topic?  is it something I can carry a semantic conflict resolution
for, in order to keep the option open to be able to merge one
without the other topic?).  Now the answer is in 'pu' and after
seeing the "Has this been resolved itself?" from Dscho, I checked
the semantic conflict resolution I have can be used when the topics
are merged to 'next' or 'master' by making trial merges, so I think
we are in good shape.

I think these two topics by themselves were both good enough to be
in 'next' for wider testing, as I do not recall any remaning issues
in the code or docs in the patches (please correct me if it is not
the case).

Thanks.

  reply	other threads:[~2019-01-19 17:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 23:20 What's cooking in git.git (Jan 2019, #03; Fri, 18) Junio C Hamano
2019-01-19  1:13 ` Elijah Newren
2019-01-19 17:50   ` Junio C Hamano [this message]
2019-01-21 15:33   ` Johannes Schindelin

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqwon0h6yx.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).