Re: [PATCH 0/5] Fix and extend encoding handling in fast export/import
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Apr 26, 2019, 21:32 UTC
- Message-ID
- <20190426213241.GP6316@genre.crustytoothpaste.net>
- In-Reply-To
- <CABPp-BEsSpFYVto2E998n-UUwD6UcVRVP61VPVg1nEgRUL1UzQ@mail.gmail.com>
On Thu, Apr 25, 2019 at 09:55:11AM -0600, Elijah Newren wrote:
Show 11 quoted lines
> On Thu, Apr 25, 2019 at 9:51 AM Elijah Newren <newren@gmail.com> wrote: > > > > While stress testing `git filter-repo`, I noticed an issue with > > encoding; further digging led to the fixes and features in this series. > > See the individual commit messages for details. > > Whoops, forgot to cc Brian; I'm curious if my understanding is correct > about the sha256sum transition plans that the intent in the short term > is using fast-export & fast-import to transition to-and-from a > sha256sum repo on the fly; if so, I believe that transition work > should use the new --reencode=yes option in patch five.
The plan is to convert using fast-import and fast-export, yes, but on the fly, no. You'll convert your repository up front using fast-import and fast-export and then conversion will happen on the fly as needed internally. The latter is a thing I'm working on.
So individual users will want to use the --reencode option, but internally we probably won't get as far as actually decoding most of the commit object, so we'll keep the bytes in place.
I do appreciate the CC, though.
-- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204