Hi,
Now that there's a released version of git that has all necessary
flags and features[1] to run git filter-repo
(https://github.com/newren/git-filter-repo), I thought I'd send an
update...
On Fri, Feb 8, 2019 at 10:53 AM Ævar Arnfjörð Bjarmason
wrote:
> On Thu, Jan 31 2019, Elijah Newren wrot
Hi Dscho,
On Fri, Feb 8, 2019 at 12:13 PM Johannes Schindelin
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 th
Hi Ævar,
On Fri, Feb 8, 2019 at 10:53 AM Ævar Arnfjörð Bjarmason
wrote:
>
> On Thu, Jan 31 2019, Elijah Newren wrote:
>
> > What's the future? (Core command of git.git? place it in contrib? keep it
> > in a separate repo?) I'm hoping to discuss that at the contributor summit
> > today, but fe
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'
On Thu, Jan 31 2019, Elijah Newren wrote:
> What's the future? (Core command of git.git? place it in contrib? keep it
> in a separate repo?) I'm hoping to discuss that at the contributor summit
> today, but feedback on the list is also welcome.
Some of this I may have mentioned at the summi
Hi Elijah,
On Thu, 7 Feb 2019, Elijah Newren wrote:
> On Thu, Jan 31, 2019 at 12:57 AM Elijah Newren wrote:
> > git-filter-repo[1], a filter-branch-like tool for rewriting repository
> > history, is ready for more widespread testing and feedback. The rough
>
> Someone at the Contributor Summit
Hi,
On Thu, Jan 31, 2019 at 12:57 AM Elijah Newren wrote:
> git-filter-repo[1], a filter-branch-like tool for rewriting repository
> history, is ready for more widespread testing and feedback. The rough
Someone at the Contributor Summit (Michael Haggerty perhaps?) asked me
about performance nu
Hi Roberto,
First of all, thanks for the feedback, and for the awesome work on BFG
repo filter!
On Fri, Feb 1, 2019 at 12:36 AM Roberto Tyley wrote:
>
> On Thu, 31 Jan 2019 at 22:37, Elijah Newren wrote:
> > On Thu, Jan 31, 2019 at 8:09 PM Junio C Hamano wrote:
> > > Elijah Newren writes:
> >
On Thu, 31 Jan 2019 at 22:37, Elijah Newren wrote:
> On Thu, Jan 31, 2019 at 8:09 PM Junio C Hamano wrote:
> > Elijah Newren writes:
> >
> > > git-filter-repo[1], a filter-branch-like tool for rewriting repository
> > > history, is ready for more widespread testing and feedback. The rough
> > >
On Thu, Jan 31, 2019 at 9:57 AM Elijah Newren wrote:
>
> Hi everyone,
>
> git-filter-repo[1], a filter-branch-like tool for rewriting repository
> history, is ready for more widespread testing and feedback.
...
> What's the future? (Core command of git.git? place it in contrib? keep it
> in a s
On Thu, Jan 31, 2019 at 8:09 PM Junio C Hamano wrote:
>
> Elijah Newren writes:
>
> > git-filter-repo[1], a filter-branch-like tool for rewriting repository
> > history, is ready for more widespread testing and feedback. The rough
> > edges I previously mentioned have been fixed, and it has seve
Elijah Newren writes:
> git-filter-repo[1], a filter-branch-like tool for rewriting repository
> history, is ready for more widespread testing and feedback. The rough
> edges I previously mentioned have been fixed, and it has several useful
> features already, though more development work is ong
Hi everyone,
git-filter-repo[1], a filter-branch-like tool for rewriting repository
history, is ready for more widespread testing and feedback. The rough
edges I previously mentioned have been fixed, and it has several useful
features already, though more development work is ongoing (docs are a
b
13 matches
Mail list logo
