git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Tan <jonathantanmy@google.com>
To: gitster@pobox.com
Cc: jonathantanmy@google.com, gitgitgadget@gmail.com,
	git@vger.kernel.org, heba.waly@gmail.com
Subject: Re: [PATCH v2 1/1] commit: display advice hints when commit fails
Date: Thu,  2 Jan 2020 11:56:37 -0800	[thread overview]
Message-ID: <20200102195637.176142-1-jonathantanmy@google.com> (raw)
In-Reply-To: <xmqq7e2cfh68.fsf@gitster-ct.c.googlers.com>

> > Junio, what are your plans over what you have in your tree? If you'd
> > like to hear Heba's opinion on it, then she can chime in; if you'd like
> > a review, then I think it's good to go in.
> 
> On hold until anything like those happens ;-) 
> 
> A random reviewer mentioning something on a patch (either in a
> line-by-line critique form or "how about doing it this way instead"
> counterproposal form) without getting followed up by others
> (including the original author) is a stall review thread, and it
> does not change the equation if the random reviewer happens to be me.

OK :-)

> > And I think the answer to that is "s" is used throughout the function in
> > various ways (in particular, used to print statuses both to stdout and
> > to the message template) so any wrapping or corralling of scope would
> > just make things more complicated. In particular, the way Heba did it in
> > v2 is more unclear - at the time of setting s->hints = 0, it's done
> 
> You mean "less clear" (just double checking if I got the negation right)?

Yes, less clear - v2 is less clear than v1.

> I think I've merged it to 'next' yesterday, but it does not mean
> that much as we are in -rc and it is not such an urgent "oops we
> broke it in this cycle, let's fix it" issue.  If we see a v3 that
> improves it, I do not mind at all reverting what I merged to 'next'
> and use the updated one instead (either way, it will be in 'master'
> during the next cycle at the earliest).

Sounds good - thanks.

  reply	other threads:[~2020-01-02 19:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17  9:17 [PATCH 0/1] [Outreachy] commit: display advice hints when commit fails Heba Waly via GitGitGadget
2019-12-17  9:17 ` [PATCH 1/1] " Heba Waly via GitGitGadget
2019-12-17 22:41   ` Junio C Hamano
2019-12-17 22:45   ` Emily Shaffer
2019-12-19  3:47     ` Heba Waly
2019-12-18  3:13   ` Jonathan Tan
2019-12-18 18:14     ` Junio C Hamano
2019-12-19  3:48     ` Heba Waly
2019-12-19  9:16 ` [PATCH v2 0/1] [Outreachy] " Heba Waly via GitGitGadget
2019-12-19  9:16   ` [PATCH v2 1/1] " Heba Waly via GitGitGadget
2019-12-19 19:14     ` Junio C Hamano
2019-12-19 19:22       ` Junio C Hamano
2019-12-19 19:47         ` Eric Sunshine
2019-12-19 19:57           ` Junio C Hamano
2019-12-20  2:31         ` Emily Shaffer
2019-12-20 18:34           ` Junio C Hamano
2019-12-20 21:39             ` Emily Shaffer
2019-12-31  0:04         ` Jonathan Tan
2019-12-31 19:06           ` Junio C Hamano
2020-01-02 19:56             ` Jonathan Tan [this message]
2019-12-19 18:26   ` [PATCH v2 0/1] [Outreachy] " Junio C Hamano
2019-12-19 18:54     ` Emily Shaffer
2019-12-19 19:23       ` Junio C Hamano
2019-12-19 19:45         ` Junio C Hamano
2019-12-21  4:37           ` Heba Waly
2019-12-21 23:54             ` Junio C Hamano
2019-12-21  5:02   ` Heba Waly

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=20200102195637.176142-1-jonathantanmy@google.com \
    --to=jonathantanmy@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=heba.waly@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.
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).