[Expo-tech] loser git conversion

[Mark Shinwell]

On Sun, 3 May 2020 at 18:44, Wookey <wookey at wookware.org> wrote:

> On 2020-05-03 18:31 +0100, Mark Shinwell wrote:
> > On Sun, 3 May 2020 at 18:27, Wookey <wookey at wookware.org> wrote:
> >
> >     I think we should get the other years
> >     working, otherwise it's a regression over the hg repo.
> >
> > I'm unsure that some of this is a regression, though.  The sorts of
> things I
> > was referring to in my previous email (e.g. changesets with discoveries
> from
> > multiple years all at once) will be in hg too.  In fact it might be worse
> > there, as I explicitly pulled back some of the changesets from a big
> ARGE merge
> > somewhere around 2013 so they were in a better position date-wise in the
> > history.
>
> True. If it's already broken in hg, then it's not a regression if it's
> broken in git too.
>
> I meant that things should process in git at at least one point for
> each year, because I'm pretty sure that was working hg. Currently
> that's not true for 2015, 2016, 2017, 2018, 2019 (IIRC).
>
> I agree that some data was in the wrong year in hg after 2013 so
> trying to fix that is an improvement. But we don't get the chance to
> re-arrange history very often, so it's worth some effort IMHO.
>

(+expo-tech@ again)

Good progress made this evening with disentangling the CVS to svn "gap"
changeset.  I probably only need another evening or two, then that will be
done.  I'm splitting out all the renames, ARGE merges, etc. into separate
changesets.

Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wookware.org/pipermail/expo-tech/attachments/20200504/7f4453fc/attachment.htm>