On 2 September 2012 15:40, Ulrich Spörlein <[email protected]> wrote: > On Sun, 2012-09-02 at 10:40:24 -0700, Artem Belevich wrote: >> On Sat, Sep 1, 2012 at 10:03 PM, Artem Belevich <[email protected]> wrote: >> > On Sat, Sep 1, 2012 at 9:29 PM, Artem Belevich <[email protected]> wrote: >> >> I've just noticed that freebsd commits on github come with a git note. >> >> If you look past the diff of the commit, you will see a note that >> >> contains path and revision number. >> >> >> >> For example: >> >> https://github.com/freebsd/freebsd/commit/fa32f1f570be8b878b2965d95b7dbdc37a953938 >> >> >> >> has a note that says: >> >> svn path=/head/; revision=239998 >> >> >> >> So, information is there, it's just not part of the log message itself >> >> unless you add '--show-notes=*' >> >> Scratch that. SVN metadata in github freebsd repo is very inconsistent. >> >> head has git-svn-id but no notes (at least I didn't see then on few >> randomly picked commits). >> >> branches have no git-svn-id, but some commits have notes with SVN info >> attached to them. >> >> The bottom line is that for many revisions it will indeed be very hard >> to figure out corresponding commit in SVN. I guess I'll be sticking >> with gitorious for the time being. > > If you read the wiki page at http://wiki.freebsd.org/GitWorkflow > carefully, you'll note: > > Known Problems > > There's still a bug in the converter, that does not incrementally > export the svn revision to git commit id mappings to so called git > "notes", instead it clobbers them always. This makes it inconvenient > to go from svn revision to git commit hash or vice versa. > > > And this is something that is and will be fixed, it's just not high on > my priority list. If someone wants to help out, that would be great!
Why isn't git.freebsd.org a straight "git svn clone" ? AFAIK that isn't broken. -- Eitan Adler _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[email protected]"
