Hi Dscho, On Fri, Feb 8, 2019 at 12:13 PM Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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
