git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ed Maste <emaste@freebsd.org>
To: Tom Clarkson <tqclarkson@icloud.com>
Cc: git mailing list <git@vger.kernel.org>
Subject: Re: git-subtree split misbehaviour with a commit having empty ls-tree for the specified subdir
Date: Tue, 28 Apr 2020 14:08:26 -0400	[thread overview]
Message-ID: <CAPyFy2CqAQWSxzVkfNqk5k=Tq_N82_62Z-rTawen9TtmdW9Ytg@mail.gmail.com> (raw)
In-Reply-To: <DB65AE2F-12DE-43B7-8B20-4E173794CAF2@icloud.com>

On Sun, 22 Dec 2019 at 08:50, Tom Clarkson <tqclarkson@icloud.com> wrote:
>
> If you want to try out my update, it’s at  https://github.com/gitgitgadget/git/pull/493. The commands I ended up with were
>
> git subtree ignore --clear-cache --prefix=contrib/elftoolchain 4d43158
> git subtree use --prefix=contrib/elftoolchain 9e78763
> git subtree split --prefix=contrib/elftoolchain 53f2672ff78be42389cf41a8258f6e9ce36808fb
>
> On my machine, ignore takes about 2 minutes to flag 200k commits as irrelevant. The split takes around 15 to go through the remaining 50k.

What's the next step with this patch set? Is there anything I can do to help?

  parent reply	other threads:[~2020-04-28 18:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22 16:55 git-subtree split misbehaviour with a commit having empty ls-tree for the specified subdir Ed Maste
2019-12-18  0:17 ` Tom Clarkson
2019-12-18 10:23   ` Ed Maste
2019-12-19  0:57     ` Tom Clarkson
2019-12-20 15:56       ` Ed Maste
2019-12-22 14:01         ` Tom Clarkson
2020-01-21 22:36           ` Ed Maste
     [not found]         ` <DB65AE2F-12DE-43B7-8B20-4E173794CAF2@icloud.com>
2020-04-28 18:08           ` Ed Maste [this message]
2020-06-17 14:46         ` Ed Maste
2020-06-18  1:13           ` Tom Clarkson

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='CAPyFy2CqAQWSxzVkfNqk5k=Tq_N82_62Z-rTawen9TtmdW9Ytg@mail.gmail.com' \
    --to=emaste@freebsd.org \
    --cc=git@vger.kernel.org \
    --cc=tqclarkson@icloud.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).