On Sun, Apr 18, 2021 at 5:47 PM Antoine Pitrou <anto...@python.org> wrote:
>
>
> Le 18/04/2021 à 17:43, Krisztián Szűcs a écrit :
> > I wouldn't overwrite the git history since there can be explicit
> > commit references in other projects.
> >
> > Either way, please don't overwrite any of the branches until I'm
> > working on the release.
>
> Ah, I think we're only talking about the arrow-rs repository here.
We should definitely apply git filter branch on the rust repositories.
>
> If however the suggestion is to do it on the main Arrow repository, then
> I'm entirely opposed to it.
The other way around hasn't occurred to me, probably I'm too focused
on apache/arrow repository at the moment.
>
> Regards
>
> Antoine.
>
>
> >
> > On Sun, Apr 18, 2021 at 5:09 PM Antoine Pitrou <anto...@python.org> wrote:
> >>
> >>
> >> Le 18/04/2021 à 16:36, Andy Grove a écrit :
> >>> Hi Wes,
> >>>
> >>> We started looking at the documentation for git filter-branch and it
> >>> recommends not to use it. It states that "git-filter-branch is riddled
> >>> with
> >>> gotchas resulting in various ways to easily corrupt repos or end up with a
> >>> mess worse than what you started with:".
> >>>
> >>> I guess we can decide to run this at any time, so let's discuss this more
> >>> once we have the repos building?
> >>
> >> A bare clone of Arrow seems to be about 81 MB (the .git directory, not
> >> the checkout). That's not huge, but not tiny either. In the end it's
> >> your decision, since the impacted people are the Rust contributors.
> >>
> >> As for `git filter-branch`, I have no experience with it, but if you run
> >> it just once and check that the repo and its contents are still valid
> >> afterwards (for example `git fsck --full`), you should be fine.
> >>
> >> Regards
> >>
> >> Antoine.
