git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Justin Donnelly <justinrdonnelly@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2022, #04; Thu, 17)
Date: Mon, 21 Mar 2022 09:51:19 -0700	[thread overview]
Message-ID: <xmqqy2131c6w.fsf@gitster.g> (raw)
In-Reply-To: <CAGTqyRzeYqXT_HXKZ794XmtD7HodvHEQeK3efUw=Pb0ObLvXPg@mail.gmail.com> (Justin Donnelly's message of "Sat, 19 Mar 2022 14:08:37 -0400")

Justin Donnelly <justinrdonnelly@gmail.com> writes:

>>* jd/prompt-upstream-mark (2022-03-03) 4 commits
>> - git-prompt: put upstream comments together
>> - git-prompt: make long upstream state indicator consistent
>> - git-prompt: make upstream state indicator location consistent
>> - git-prompt: rename `upstream` to `upstream_type`
>>
>> Tweaks in the command line prompt (in contrib/) code around its
>> GIT_PS1_SHOWUPSTREAM feature.
>>
>> What's the status of this one?
>> source: <pull.1162.v2.git.1645991832.gitgitgadget@gmail.com>
>
> I'm the author of these patches. I'm not too familiar with the
> workflow and I just want to make sure this question isn't directed at
> me and you don't need anything from me right now. Ævar provided
> initial feedback and FWIW I think these are ready to be merged.

I am asking both people who use "git prompt" (they would hopefully
care, as new breakages would inconvenience them) if they mind this
series to appear in future releases in "Git" in its current form,
and who wrote the series (that's you) how ready the series is.

Thanks for giving one of the two halves I wanted ;-)


  reply	other threads:[~2022-03-21 16:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19 18:08 What's cooking in git.git (Mar 2022, #04; Thu, 17) Justin Donnelly
2022-03-21 16:51 ` Junio C Hamano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-17 11:34 Junio C Hamano
2022-03-22  1:25 ` Taylor Blau
2022-03-23 18:27   ` Junio C Hamano
2022-03-23 19:20     ` Taylor Blau
2022-03-23 21:37       ` Junio C Hamano
2022-03-23 21:47         ` Taylor Blau
2022-03-22 18:24 ` Jeff Hostetler
2022-03-23 18:28   ` Junio C Hamano
2022-03-23 20:14     ` Jeff Hostetler

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=xmqqy2131c6w.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=justinrdonnelly@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).