git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: What's cooking in git.git (Apr 2020, #03; Tue, 28)
Date: Wed, 29 Apr 2020 10:23:39 -0700	[thread overview]
Message-ID: <xmqqy2qew6hw.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200429165501.GC83442@syl.local> (Taylor Blau's message of "Wed, 29 Apr 2020 10:55:01 -0600")

Taylor Blau <me@ttaylorr.com> writes:

> Right... but I'm not sure that I agree that this other topic "builds" on
> the whole series. There is nothing in the last commit that the other
> series is dependent on. So, I was suggesting something like:
>
>   $ git checkout tb/commit-graph-split-strategy
>   $ git revert HEAD
>   $ git checkout tb/commit-graph-fd-exhaustion-fix
>   $ git rebase tb/commit-graph-split-strategy # making sure to drop the final patch

We cannot do this, as fd-exhaustion-fix is already in 'next'.

>> Why don't we do this:
>>
>>  $ git checkout tb/commit-graph-fd-exhaustion-fix
>>  $ git revert tb/commit-graph-split-strategy
>>  $ git checkout master
>>  $ git merge tb/commit-graph-fd-exhaustion-fix
>>  $ git branch -d tb/commit-graph-fd-exhaustion-fix tb/commit-graph-split-strategy
>
> That's fine with me, too.
>
>> That's the simplest solution and we'll have two fewer topics we need
>> to worry about when we are done.

OK.

  reply	other threads:[~2020-04-29 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 23:41 What's cooking in git.git (Apr 2020, #03; Tue, 28) Junio C Hamano
2020-04-29 15:57 ` Taylor Blau
2020-04-29 16:45   ` Junio C Hamano
2020-04-29 16:55     ` Taylor Blau
2020-04-29 17:23       ` Junio C Hamano [this message]
2020-04-29 17:26         ` Taylor Blau

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=xmqqy2qew6hw.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    --cc=szeder.dev@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).