All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: tb/cruft-packs
Date: Thu, 06 Jan 2022 10:21:41 -0800	[thread overview]
Message-ID: <xmqqlezsend6.fsf@gitster.g> (raw)
In-Reply-To: <Ydcev8HqCjycBJS+@nand.local> (Taylor Blau's message of "Thu, 6 Jan 2022 11:54:23 -0500")

Taylor Blau <me@ttaylorr.com> writes:

> Feel free to eject this for the time being, especially if it makes
> managing your tree any more convenient. I have a few small things that I
> want to adjust before sending a new version, which likely won't happen
> until after we have finished the 2.35 cycle.

Carrying a topic branch that is not even merged to 'seen' is a
no-cost thing for me.  I'll mark it discarded, but may keep the
actual topic to make it easier to see the range-diff when we see a
reroll.

Thanks.

      reply	other threads:[~2022-01-06 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06  1:56 What's cooking in git.git (Jan 2022, #02; Wed, 5) Junio C Hamano
2022-01-06 16:53 ` Taylor Blau
2022-01-06 16:54 ` tb/cruft-packs (was: Re: What's cooking in git.git (Jan 2022, #02; Wed, 5)) Taylor Blau
2022-01-06 18:21   ` Junio C Hamano [this message]

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=xmqqlezsend6.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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 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.