All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2020, #04; Mon, 22)
Date: Tue, 23 Jun 2020 12:16:21 -0700	[thread overview]
Message-ID: <xmqqbll9d24a.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2006231445190.54@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Tue, 23 Jun 2020 14:46:21 +0200 (CEST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> Hi Junio,
>
> On Mon, 22 Jun 2020, Junio C Hamano wrote:
>
>> The 'pu' (proposed updates) branch has been renamed to 'seen' to use
>> a more meaningful name (after all, the purpose of it is not to
>> contain all proposals, but to merely serve as a place to park what
>> the maintainer happened to have seen) and more importantly, to make
>> room for topics from those contributors whose two-letter name
>> abbreviation needs to be 'pu' under 'pu/$topicName'.
>
> Very nice!
>
> I apologize in advance for taking a while to get GitGitGadget back on
> track after this rename, as I had originally planned to work on other
> things this week.

Sorry, I didn't expect that tools including GGG cares about 'pu' (I
expected some to care about 'master' and/or 'maint' to detect "there
is nothing remaining to ask to be pulled", though).

Thanks for quickly attending to necessary updates.


  reply	other threads:[~2020-06-23 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23  0:54 What's cooking in git.git (Jun 2020, #04; Mon, 22) Junio C Hamano
2020-06-23 10:00 ` Jeff King
2020-06-23 12:46 ` Johannes Schindelin
2020-06-23 19:16   ` Junio C Hamano [this message]
2020-06-28 19:22 ` `seen' datapoint [was: What's cooking in git.git (Jun 2020, #04; Mon, 22)] Eric Wong
2020-06-29  1:22   ` `seen' datapoint [ Junio C Hamano
2020-06-29  2:04     ` Eric Wong
2020-06-29 18:45       ` Jeff King
2020-06-29 19:03         ` Eric Wong

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=xmqqbll9d24a.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.