Re: [eigen] Bitbucket migration

2019-09-12 Thread Christoph Hertzberg 




On 12/09/2019 01.27, Gael Guennebaud wrote:

On Wed, Sep 11, 2019 at 6:50 PM Christoph Hertzberg <
c...@informatik.uni-bremen.de> wrote:

[...]
Did we actually plan to migrate bugzilla to gitlab-issues as well?
Would we do this by just creating new issues with a link to the
bz-archive? (This would be only slightly inconvenient if discussions are
split, but that's ok, IMO)


See this first attempt:
https://gitlab.inria.fr/guenneba/eigen-bzmigration-test1/issues
Almost everything is preserved including the bug's ID. We can also
automatically mark the bz bugs as "MOVED" with a link to the respective
gitlab entry.


Oh, I now found this link in the other thread as well. I guess one 
problem here is that we would have both PRs and Bugs starting with #1 
Sure, it is possible to remap one of these, but that might be confusing 
as well.



Christoph



--
 Dr.-Ing. Christoph Hertzberg

 Besuchsadresse der Nebengeschäftsstelle:
 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 5
 28359 Bremen, Germany

 Postadresse der Hauptgeschäftsstelle Standort Bremen:
 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 1
 28359 Bremen, Germany

 Tel.: +49 421 178 45-4021
 Zentrale: +49 421 178 45-0
 E-Mail:   christoph.hertzb...@dfki.de

 Weitere Informationen: http://www.dfki.de/robotik
  -
  Deutsches Forschungszentrum für Künstliche Intelligenz GmbH
  Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany

  Geschäftsführung:
  Prof. Dr. Jana Koehler (Vorsitzende)
  Dr. Walter Olthoff

  Vorsitzender des Aufsichtsrats:
  Prof. Dr. h.c. Hans A. Aukes
  Amtsgericht Kaiserslautern, HRB 2313
  -

Re: [eigen] Bitbucket migration

2019-09-12 Thread Joseph Mirabel 
To summarize what is missing:

- there are a lot of "backporting rev[0-9]+" that are not found. I don't
know what "backporting" means. I just know that "hg log --rev N" for all
the one I tested returns "unknown revision".

  I guess I could fix most of them by adding some of the main developers
remote (remote in git sense). This would work only if the same run of
fast-export converts all Eigen mercurial repos at once and then everyone
picks its own git parts from this. Using a map of hg->git hashes should
allow us to rebuild the individual git repos automatically.

- I do not catch ranges of revision number like "[0-9]+-[0-9]+". It
wouldn't be hard to achieve.

- what about unamed hg heads ? Should we drop them ? If not, I would
appreciate if someone knowing mercurial could name them (with a name
valid for hg and git).


Joseph


Le 12/09/2019 à 00:37, Gael Guennebaud a écrit :
>
>
> On Wed, Sep 11, 2019 at 7:38 PM Joseph Mirabel  > wrote:
>
> Dear Eigen developers,
>
> - I can convert all reference like to revisions or mercurial
> hashes that
> follows the regex in [2].
>
>
> I'll look at it more carefully later, but... wow!! this looks very
> promising: https://github.com/jmirabel/eigen_tmp/commit/6e53e31dc2d79da
>  
> For comparison, the same commit in our official
> git-mirror: 
> https://github.com/eigenteam/eigen-git-mirror/commit/6ba9310bc2c168
>
> gael
>
>
> - I did not try to convert URLs although it should not be hard.
>
> - I manually edited the author file [5] so that they would fit git
> author format. If you find yourself in the list and want to update it,
> you can contact me.
>
>
> It should not be hard to add more rules to the plugin
> convert_references
> if anyone feels like doing it.
>
>
> Best,
>
> Joseph
>
>
> [1] https://github.com/frej/fast-export.git
>
> [2]
> 
> https://github.com/jmirabel/fast-export/blob/1fdc76e0626acd6adfcc0d900d14f36b459c4798/plugins/convert_references/__init__.py#L16
>
> [3] https://github.com/jmirabel/fast-export
>
> [4] https://github.com/jmirabel/eigen_tmp.git
>
> [5]
> https://github.com/jmirabel/fast-export/blob/master/eigen/authors_reworked
>
>
>
> Le 11/09/2019 à 18:03, Gael Guennebaud a écrit :
> > To prepare the migration from bitbucket, I started to play a bit
> with
> > its API to see what could be done. So far I've quickly draft two
> > (ugly) python scripts to archive the forks and pull-requests. Since
> > this is a one shot for us, I did not cared about robustness, safety,
> > generality, beauty, etc.
> >
> > You can see them there
> > : https://gitlab.com/ggael/bitbucket-migration-tools and contribute!
> >
> > ** Forks **
> >
> > You can see the summary of the fork script
> > there: http://manao.inria.fr/eigen_tmp/archive_forks_log.html
> >
> > The hg clones (history+checkout) represents 20GB, maybe 12GB if we
> > remove the checkouts. Among the 460 forks, 214 seems to have no
> change
> > at all (according to "hg out") and could be dropped. I don't
> know yet
> > where to host them though.
> >
> > This script can be ran incrementally.
> >
> >
> > ** Pull-Requests **
> >
> > You can find the output of the pull-requests script
> > there: http://manao.inria.fr/eigen_tmp/pullrequests/
> >
> > There is a short summary, and then for each PR a static .html file
> > plus diff/patch files, and other details. For instance,
> >
> see: http://manao.inria.fr/eigen_tmp/pullrequests/OPEN/686/pr686.html
> >
> > Currently this script cannot be ran incrementally. You have to
> run it
> > just before closing the respective repository!
> >
> > Also, this script does not grab inline comments. Only the main
> > discussions is archived. Those can be obtained by iterating over the
> > "activity" pages, but I don't think that's worth the effort because
> > they would be difficult to exploit anyway.
> >
> >
> > ** hg to git **
> >
> > As discussed in the other thread, if we switch from hg to git, then
> > all hashes will have to be updated. Generating a map file is
> easy, and
> > thus updating the links/hashes in bug comments and PR comments
> should
> > not be too difficult (we only have to figure out the right regex to
> > catch all variants).
> >
> > However, updating the hashes within the commit messages will require
> > to rewrite the whole history in a careful order. Does anyone here
> > feels brave enough to write such a script? If not, I guess we could
> > live with an online php script doing the hash conversion on
> demand. I
> > don't think we'll have to follow such hashes so frequently.
> >
> > cheers,
> > gael
> >
> >
>
>
>

Re: [eigen] Bitbucket migration

2019-09-12 Thread Gael Guennebaud 
On Thu, Sep 12, 2019 at 12:59 AM David Tellenbach <
david.tellenb...@tellnotes.org> wrote:

> But is it our responsibility to archive such forks? There could be forks
> for personal purpose only with no intend to create a PR at all. Should we
> really bother to archive these? (At least) everyone with a mercurial repo
> on bitbucket has received an email that mercurial support will be dropped.
> If someone thinks his fork is worth keeping, the person should archive it
> or open a PR. I think the keeping the changesets of all PRs is enough.
>

We're talking about open-source code. IMO this should be the responsibility
of bitbucket to keep them read-only for a few more years. Anyways, I
already have them archived on my computer, so that's a minor aspect. Let's
focus on the other ones.


>
>> > ** Pull-Requests **
>>
>> Does gitlab allow to map "[Bb]ug (\d+)" to (an archive of) our bugzilla
>> page and "\#(\d+)" to either the archived old PRs or new PRs/issues? (if
>> need be, we could manually create issues #1 to #7xx with just a link to
>> the archived PRs.
>>
>
> I haven't check that yet.
>
>
> If there's no possibility to automatically forward Bugs/PRs, it should
> again be possible to create those automatically using the GitLab API.
>

In gitlab issues are referenced with #123 and merge-requests with !123 (see
https://docs.gitlab.com/ee/user/markdown.html#special-gitlab-references)

So when switching from hg to git, we could do: "([Bb]ug) (\d+)" -> "\2 #\1"
in the commit messages. For bug comments, this change is already taken care
by the bz2gitlab migration script.

For old pullrequests, it is possible to automatically link WHATEVER-XYZ to
https://some_url/XYZ via the "custom issue tracker" service. Demo:
https://gitlab.inria.fr/guenneba/eigen-bzmigration-test2/issues/1#note_234549
So we could rewrite old PR references as PR-XYZ. One shortcoming though is
that you cannot configure what "WHATEVER" is. The underlying matching regex
seems to be as general as: "[a-zA-Z]-(\d+)". Still ok I guess.


> Another topic: How about creating a gitlab.com group (since eigen is
> taken I suggest eigen-official) and create a migration repo where we host
> all the migration stuff and scripts?
>

I've asked the owner of gitlab.com/eigen last week to see if he would be
super kind to release the "eigen" username for us (as it seems to be used
by himself only), but no answer yet. Without a positive answer we could
think about:

eigen-official
eigen-team
libeigen

gael



>
> David
>
> On 11. Sep 2019, at 23:27, Gael Guennebaud 
> wrote:
>
>
>
> On Wed, Sep 11, 2019 at 6:50 PM Christoph Hertzberg <
> c...@informatik.uni-bremen.de> wrote:
>
>>
>> > ** Forks **
>> >
>> > You can see the summary of the fork script there:
>> > http://manao.inria.fr/eigen_tmp/archive_forks_log.html
>> >
>> > The hg clones (history+checkout) represents 20GB, maybe 12GB if we
>> remove
>> > the checkouts. Among the 460 forks, 214 seems to have no change at all
>> > (according to "hg out") and could be dropped. I don't know yet where to
>> > host them though.
>>
>> I think it is sufficient if we host a (frozen) version of the main
>> repository (probably simply at tuxfamily). I think many forks don't have
>> changes, because they actually got merged.
>> And I don't think we need to host any of the forks, as long as we have
>> the changesets in the archived PRs.
>>
>
> I don't think all forks with changes have a related PRs, but forks
> exhibiting changes and that are associated to a close PR can probably be
> ignored too.
>
>
>>
>> > ** Pull-Requests **
>>
>> Does gitlab allow to map "[Bb]ug (\d+)" to (an archive of) our bugzilla
>> page and "\#(\d+)" to either the archived old PRs or new PRs/issues? (if
>> need be, we could manually create issues #1 to #7xx with just a link to
>> the archived PRs.
>>
>
> I haven't check that yet.
>
> Did we actually plan to migrate bugzilla to gitlab-issues as well?
>> Would we do this by just creating new issues with a link to the
>> bz-archive? (This would be only slightly inconvenient if discussions are
>> split, but that's ok, IMO)
>>
>
> See this first attempt:
> https://gitlab.inria.fr/guenneba/eigen-bzmigration-test1/issues
> Almost everything is preserved including the bug's ID. We can also
> automatically mark the bz bugs as "MOVED" with a link to the respective
> gitlab entry.
> I'll share the updated bz2gitlab migration script asap. My main concern
> about gitlab issues is that comments are not searchable, only the
> description is.
>
> gael
>
> > ** hg to git **
>> >
>> > However, updating the hashes within the commit messages will require to
>> > rewrite the whole history in a careful order. Does anyone here feels
>> brave
>> > enough to write such a script? If not, I guess we could live with an
>> online
>> > php script doing the hash conversion on demand. I don't think we'll
>> have to
>> > follow such hashes so frequently.
>>
>> I agree that it won't be required that often (most "grafted from"

Re: [eigen] Bitbucket migration

2019-09-12 Thread Gael Guennebaud 
On Thu, Sep 12, 2019 at 9:53 AM Joseph Mirabel 
wrote:

> To summarize what is missing:
>
> - there are a lot of "backporting rev[0-9]+" that are not found. I don't
> know what "backporting" means. I just know that "hg log --rev N" for all
> the one I tested returns "unknown revision".
>

$ hg log -v  | grep "backporting"  does not give me that many:

backporting 1784: fixed bug #62

-> For this one "hg log -r 1784" tells me that the true hash is
0430786c2a6f (but we don't care if we lost one link!)

The followings are very old subversion references, we don't care at all:

backporting 964177 (gcc 3.3 fix)
backporting r964165 (gcc 3.3 fixes)
backporting rev 951682 (compilation fix in aligned allocator)
backporting rev 918446: fix MSVC internal compilation error
backporting rev925153 (bugfix in MapBase::coeffRef(int) )
backporting commit 918468 (fix MSVC internal error)


> - I do not catch ranges of revision number like "[0-9]+-[0-9]+". It
> wouldn't be hard to achieve.
>
-> I could not find any meaningful one.

I only found two meaningful "([0-9]+:)([0-9]+)" occurrences like:
6089:76b6c62565a6. In this case, if \2 is a valid hash, then \1 (e.g.,
"6089:") should be dropped to enable auto-link creation, see:
https://github.com/jmirabel/eigen_tmp/commit/4325f05a4b60

But that's really no big deal as the true hash has been properly updated,
and there are only 2 occurrences!

> - what about unamed hg heads ? Should we drop them ? If not, I would
> appreciate if someone knowing mercurial could name them (with a name valid
> for hg and git).
>
I guess this issue is related to changeset 59a7e404a93c, which is an empty
commit closing a branch. If your script ignores it without additional
issue, then that's fine.

So for me this is all good, I would only care about updating references to
bugs/PR by applying the following substitutions:

"([Bb]ug) (\d+)" -> "\2 #\1"
"bugs (\d+) and (\d+)" -> "bugs #\1 and #\2"
"http://eigen.tuxfamily.org/bz/show_bug.cgi\?id=(\d+)" -> "#\1"
"[Pp]ull [Rr]equest #(\d+)" -> "pull request PR-\1"
"PR #(\d+)" -> "PR-\1"


gael


>
> Joseph
>
>
> Le 12/09/2019 à 00:37, Gael Guennebaud a écrit :
>
>
>
> On Wed, Sep 11, 2019 at 7:38 PM Joseph Mirabel 
> wrote:
>
>> Dear Eigen developers,
>>
>> - I can convert all reference like to revisions or mercurial hashes that
>> follows the regex in [2].
>>
>
> I'll look at it more carefully later, but... wow!! this looks very
> promising: https://github.com/jmirabel/eigen_tmp/commit/6e53e31dc2d79da
>
> For comparison, the same commit in our official git-mirror:
> https://github.com/eigenteam/eigen-git-mirror/commit/6ba9310bc2c168
>
> gael
>
>
>> - I did not try to convert URLs although it should not be hard.
>>
>> - I manually edited the author file [5] so that they would fit git
>> author format. If you find yourself in the list and want to update it,
>> you can contact me.
>>
>>
>> It should not be hard to add more rules to the plugin convert_references
>> if anyone feels like doing it.
>>
>>
>> Best,
>>
>> Joseph
>>
>>
>> [1] https://github.com/frej/fast-export.git
>>
>> [2]
>>
>> https://github.com/jmirabel/fast-export/blob/1fdc76e0626acd6adfcc0d900d14f36b459c4798/plugins/convert_references/__init__.py#L16
>>
>> [3] https://github.com/jmirabel/fast-export
>>
>> [4] https://github.com/jmirabel/eigen_tmp.git
>>
>> [5]
>> https://github.com/jmirabel/fast-export/blob/master/eigen/authors_reworked
>>
>>
>>
>> Le 11/09/2019 à 18:03, Gael Guennebaud a écrit :
>> > To prepare the migration from bitbucket, I started to play a bit with
>> > its API to see what could be done. So far I've quickly draft two
>> > (ugly) python scripts to archive the forks and pull-requests. Since
>> > this is a one shot for us, I did not cared about robustness, safety,
>> > generality, beauty, etc.
>> >
>> > You can see them there
>> > : https://gitlab.com/ggael/bitbucket-migration-tools and contribute!
>> >
>> > ** Forks **
>> >
>> > You can see the summary of the fork script
>> > there: http://manao.inria.fr/eigen_tmp/archive_forks_log.html
>> >
>> > The hg clones (history+checkout) represents 20GB, maybe 12GB if we
>> > remove the checkouts. Among the 460 forks, 214 seems to have no change
>> > at all (according to "hg out") and could be dropped. I don't know yet
>> > where to host them though.
>> >
>> > This script can be ran incrementally.
>> >
>> >
>> > ** Pull-Requests **
>> >
>> > You can find the output of the pull-requests script
>> > there: http://manao.inria.fr/eigen_tmp/pullrequests/
>> >
>> > There is a short summary, and then for each PR a static .html file
>> > plus diff/patch files, and other details. For instance,
>> > see: http://manao.inria.fr/eigen_tmp/pullrequests/OPEN/686/pr686.html
>> >
>> > Currently this script cannot be ran incrementally. You have to run it
>> > just before closing the respective repository!
>> >
>> > Also, this script does not grab inline comments. Only the main
>> > discussions is archived. Those can be obtained by iterating over the

Re: [eigen] Bitbucket migration

2019-09-12 Thread Gael Guennebaud 
On Thu, Sep 12, 2019 at 4:50 PM Christoph Hertzberg <
c...@informatik.uni-bremen.de> wrote:

> Small question, maybe I'm just missing it:
> Did you actually translate the 3.x, 2.0 branches as well or just the
> default/master branch?
>

I just ran the script, and all branches and tags are there, so I guess he
only pushed the master branch.

I'd actually be fine with filtering out all other named branches ...
>

Of course we should keep only 2.0 , 3.0, 3.1, 3.2, 3.3, and master and
ignore the others.


> Also, is it possible to apply the tags (from ./.hgtags)?
>

same, you have to "git push --tags"

See: https://gitlab.com/ggael/eigen-tmp (I pushed all branches :( )

gael


>
> But I agree, great work!
> Christoph
>
> On 12/09/2019 16.41, Gael Guennebaud wrote:
> > Excellent! Thanks a lot!
> >
> > Do you have a hash translation table in some form that I could use in the
> > other scripts?
> >
> > gael
> >
> > On Thu, Sep 12, 2019 at 1:46 PM Joseph Mirabel 
> > wrote:
> >
> >> Hello Gael,
> >>
> >> I applied the changes you requested and force-pushed to
> >> github.com/jmirabel/eigen_tmp
> >>
> >> Joseph
> >>
> >>
> >> Le 12/09/2019 à 11:46, Gael Guennebaud a écrit :
> >>>
> >>> So for me this is all good, I would only care about updating
> >>> references to bugs/PR by applying the following substitutions:
> >>>
> >>> "([Bb]ug) (\d+)" -> "\2 #\1"
> >>> "bugs (\d+) and (\d+)" -> "bugs #\1 and #\2"
> >>> "http://eigen.tuxfamily.org/bz/show_bug.cgi\?id=(\d+)
> 
> >> " -> "#\1"
> >>> "[Pp]ull [Rr]equest #(\d+)" -> "pull request PR-\1"
> >>> "PR #(\d+)" -> "PR-\1"
> >>
> >>
> >>
> >
>
> --
>   Dr.-Ing. Christoph Hertzberg
>
>   Besuchsadresse der Nebengeschäftsstelle:
>   DFKI GmbH
>   Robotics Innovation Center
>   Robert-Hooke-Straße 5
>   28359 Bremen, Germany
>
>   Postadresse der Hauptgeschäftsstelle Standort Bremen:
>   DFKI GmbH
>   Robotics Innovation Center
>   Robert-Hooke-Straße 1
>   28359 Bremen, Germany
>
>   Tel.: +49 421 178 45-4021
>   Zentrale: +49 421 178 45-0
>   E-Mail:   christoph.hertzb...@dfki.de
>
>   Weitere Informationen: http://www.dfki.de/robotik
>-
>Deutsches Forschungszentrum für Künstliche Intelligenz GmbH
>Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany
>
>Geschäftsführung:
>Prof. Dr. Jana Koehler (Vorsitzende)
>Dr. Walter Olthoff
>
>Vorsitzender des Aufsichtsrats:
>Prof. Dr. h.c. Hans A. Aukes
>Amtsgericht Kaiserslautern, HRB 2313
>-
>
>
>
>

Re: [eigen] Bitbucket migration

2019-09-12 Thread Gael Guennebaud 
Excellent! Thanks a lot!

Do you have a hash translation table in some form that I could use in the
other scripts?

gael

On Thu, Sep 12, 2019 at 1:46 PM Joseph Mirabel 
wrote:

> Hello Gael,
>
> I applied the changes you requested and force-pushed to
> github.com/jmirabel/eigen_tmp
>
> Joseph
>
>
> Le 12/09/2019 à 11:46, Gael Guennebaud a écrit :
> >
> > So for me this is all good, I would only care about updating
> > references to bugs/PR by applying the following substitutions:
> >
> > "([Bb]ug) (\d+)" -> "\2 #\1"
> > "bugs (\d+) and (\d+)" -> "bugs #\1 and #\2"
> > "http://eigen.tuxfamily.org/bz/show_bug.cgi\?id=(\d+)
> " -> "#\1"
> > "[Pp]ull [Rr]equest #(\d+)" -> "pull request PR-\1"
> > "PR #(\d+)" -> "PR-\1"
>
>
>

Re: [eigen] Bitbucket migration

2019-09-12 Thread Christoph Hertzberg 

Small question, maybe I'm just missing it:
Did you actually translate the 3.x, 2.0 branches as well or just the 
default/master branch?


I'd actually be fine with filtering out all other named branches ...

Also, is it possible to apply the tags (from ./.hgtags)?

But I agree, great work!
Christoph

On 12/09/2019 16.41, Gael Guennebaud wrote:

Excellent! Thanks a lot!

Do you have a hash translation table in some form that I could use in the
other scripts?

gael

On Thu, Sep 12, 2019 at 1:46 PM Joseph Mirabel 
wrote:


Hello Gael,

I applied the changes you requested and force-pushed to
github.com/jmirabel/eigen_tmp

Joseph


Le 12/09/2019 à 11:46, Gael Guennebaud a écrit :


So for me this is all good, I would only care about updating
references to bugs/PR by applying the following substitutions:

"([Bb]ug) (\d+)" -> "\2 #\1"
"bugs (\d+) and (\d+)" -> "bugs #\1 and #\2"
"http://eigen.tuxfamily.org/bz/show_bug.cgi\?id=(\d+)

" -> "#\1"

"[Pp]ull [Rr]equest #(\d+)" -> "pull request PR-\1"
"PR #(\d+)" -> "PR-\1"








--
 Dr.-Ing. Christoph Hertzberg

 Besuchsadresse der Nebengeschäftsstelle:
 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 5
 28359 Bremen, Germany

 Postadresse der Hauptgeschäftsstelle Standort Bremen:
 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 1
 28359 Bremen, Germany

 Tel.: +49 421 178 45-4021
 Zentrale: +49 421 178 45-0
 E-Mail:   christoph.hertzb...@dfki.de

 Weitere Informationen: http://www.dfki.de/robotik
  -
  Deutsches Forschungszentrum für Künstliche Intelligenz GmbH
  Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany

  Geschäftsführung:
  Prof. Dr. Jana Koehler (Vorsitzende)
  Dr. Walter Olthoff

  Vorsitzender des Aufsichtsrats:
  Prof. Dr. h.c. Hans A. Aukes
  Amtsgericht Kaiserslautern, HRB 2313
  -

Re: [eigen] Bitbucket migration

2019-09-12 Thread Christoph Hertzberg 

Ah sorry, I should have tried that locally myself :)

Christoph

On 12/09/2019 17.18, Gael Guennebaud wrote:

On Thu, Sep 12, 2019 at 4:50 PM Christoph Hertzberg <
c...@informatik.uni-bremen.de> wrote:


Small question, maybe I'm just missing it:
Did you actually translate the 3.x, 2.0 branches as well or just the
default/master branch?



I just ran the script, and all branches and tags are there, so I guess he
only pushed the master branch.

I'd actually be fine with filtering out all other named branches ...




Of course we should keep only 2.0 , 3.0, 3.1, 3.2, 3.3, and master and
ignore the others.



Also, is it possible to apply the tags (from ./.hgtags)?



same, you have to "git push --tags"

See: https://gitlab.com/ggael/eigen-tmp (I pushed all branches :( )

gael




But I agree, great work!
Christoph

On 12/09/2019 16.41, Gael Guennebaud wrote:

Excellent! Thanks a lot!

Do you have a hash translation table in some form that I could use in the
other scripts?

gael

On Thu, Sep 12, 2019 at 1:46 PM Joseph Mirabel 
wrote:


Hello Gael,

I applied the changes you requested and force-pushed to
github.com/jmirabel/eigen_tmp

Joseph


Le 12/09/2019 à 11:46, Gael Guennebaud a écrit :


So for me this is all good, I would only care about updating
references to bugs/PR by applying the following substitutions:

"([Bb]ug) (\d+)" -> "\2 #\1"
"bugs (\d+) and (\d+)" -> "bugs #\1 and #\2"
"http://eigen.tuxfamily.org/bz/show_bug.cgi\?id=(\d+)



" -> "#\1"

"[Pp]ull [Rr]equest #(\d+)" -> "pull request PR-\1"
"PR #(\d+)" -> "PR-\1"








--
   Dr.-Ing. Christoph Hertzberg

   Besuchsadresse der Nebengeschäftsstelle:
   DFKI GmbH
   Robotics Innovation Center
   Robert-Hooke-Straße 5
   28359 Bremen, Germany

   Postadresse der Hauptgeschäftsstelle Standort Bremen:
   DFKI GmbH
   Robotics Innovation Center
   Robert-Hooke-Straße 1
   28359 Bremen, Germany

   Tel.: +49 421 178 45-4021
   Zentrale: +49 421 178 45-0
   E-Mail:   christoph.hertzb...@dfki.de

   Weitere Informationen: http://www.dfki.de/robotik
-
Deutsches Forschungszentrum für Künstliche Intelligenz GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany

Geschäftsführung:
Prof. Dr. Jana Koehler (Vorsitzende)
Dr. Walter Olthoff

Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
-








--
 Dr.-Ing. Christoph Hertzberg

 Besuchsadresse der Nebengeschäftsstelle:
 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 5
 28359 Bremen, Germany

 Postadresse der Hauptgeschäftsstelle Standort Bremen:
 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 1
 28359 Bremen, Germany

 Tel.: +49 421 178 45-4021
 Zentrale: +49 421 178 45-0
 E-Mail:   christoph.hertzb...@dfki.de

 Weitere Informationen: http://www.dfki.de/robotik
  -
  Deutsches Forschungszentrum für Künstliche Intelligenz GmbH
  Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany

  Geschäftsführung:
  Prof. Dr. Jana Koehler (Vorsitzende)
  Dr. Walter Olthoff

  Vorsitzender des Aufsichtsrats:
  Prof. Dr. h.c. Hans A. Aukes
  Amtsgericht Kaiserslautern, HRB 2313
  -

Re: [eigen] Bitbucket migration

2019-09-12 Thread Joseph Mirabel 
I added a commit on my fork of fast-export which generate a file with
lines as

hg_rev_number hg_hash git_hash


I pushed it to https://github.com/jmirabel/eigen_tmp/blob/master/hg2git-map

Obviously, it should be put in another place.


fast-export can also add hg hashes as notes to git commits. That may be
a good place as well.


Joseph


Le 12/09/2019 à 16:41, Gael Guennebaud a écrit :
>
> Excellent! Thanks a lot!
>
> Do you have a hash translation table in some form that I could use in
> the other scripts?
>
> gael
>
> On Thu, Sep 12, 2019 at 1:46 PM Joseph Mirabel  > wrote:
>
> Hello Gael,
>
> I applied the changes you requested and force-pushed to
> github.com/jmirabel/eigen_tmp 
>
> Joseph
>
>
> Le 12/09/2019 à 11:46, Gael Guennebaud a écrit :
> >
> > So for me this is all good, I would only care about updating
> > references to bugs/PR by applying the following substitutions:
> >
> > "([Bb]ug) (\d+)" -> "\2 #\1"
> > "bugs (\d+) and (\d+)" -> "bugs #\1 and #\2"
> > "http://eigen.tuxfamily.org/bz/show_bug.cgi\?id=(\d+)
> " -> "#\1"
> > "[Pp]ull [Rr]equest #(\d+)" -> "pull request PR-\1"
> > "PR #(\d+)" -> "PR-\1"
>
>