git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: New command/tool: git filter-repo
Date: Mon, 11 Feb 2019 08:00:30 -0800	[thread overview]
Message-ID: <CABPp-BEhjkP4kUgT9unhbM5kzykEwcP1bnrhFKQ+N9Ci9ZY=eg@mail.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1902082111320.41@tvgsbejvaqbjf.bet>

Hi Dscho,

On Fri, Feb 8, 2019 at 12:13 PM Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>
> Hi Ævar,
>
> On Fri, 8 Feb 2019, Ævar Arnfjörð Bjarmason wrote:
>
> > [...]
> >
> >   But perhaps there's ways we can in advance deal with a potential
> >   future breaking API change. E.g. some Pythonic way of versioning the
> >   API, or just prominently documenting whatever (low?) stability
> >   guarantees we're making.
>
> Another thing to keep in mind: it being in Python prevents it from being
> distributed with Git for Windows. The Git for Windows installer already
> weighs way more than it used to (it used to be under 30MB, now it is
> 44MB), and I am simply not willing to increase the footprint dramatically
> just for one rarely used command.

That would be unfortunate, though understandable.  I am curious,
though: do you include and does anyone use filter-branch on windows?
You mentioned elsewhere in this thread that you weren't even willing
to attempt to run filter-branch there.  If people aren't using
filter-branch on windows, then there's nothing for me to save them
from anyway.  If they are, I'm curious to hear more about the usecases
and motivations, even if the cost of my tool is too high for you to
include.

Also, since filter-branch and filter-repo are meant mostly as one-shot
migration tools, it is already not uncommon for people to do it on a
different machine (perhaps one with more RAM, or faster disks), and at
most one person on the team needs to run it (sometimes folks even look
to an "expert" outside the team to run the migration for them).  Once
migrated, they push the results back and are done with the tool.

> If only it were written as a built-in...

A built-in would be great, IF it could provide all the same
capabilities and with at least the same speed.  However, making it a
built-in would fundamentally remove a significant chunk of its power
and flexibility, which was part of the driving force for creating this
tool.

Elijah

  reply	other threads:[~2019-02-11 16:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31  8:57 New command/tool: git filter-repo Elijah Newren
2019-01-31 19:09 ` Junio C Hamano
2019-01-31 20:43   ` Elijah Newren
2019-01-31 23:36     ` Roberto Tyley
2019-02-01  7:38       ` Elijah Newren
2019-01-31 20:47 ` Elijah Newren
2019-02-08  1:25 ` Elijah Newren
2019-02-08 10:22   ` Johannes Schindelin
2019-02-08 18:53 ` Ævar Arnfjörð Bjarmason
2019-02-08 20:13   ` Johannes Schindelin
2019-02-11 16:00     ` Elijah Newren [this message]
2019-02-11 15:47   ` Elijah Newren
2019-06-08 16:20   ` Elijah Newren

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='CABPp-BEhjkP4kUgT9unhbM5kzykEwcP1bnrhFKQ+N9Ci9ZY=eg@mail.gmail.com' \
    --to=newren@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=avarab@gmail.com \
    --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.
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).