|
From: Daniel J S. <dan...@ie...> - 2017-10-16 19:39:59
|
On 10/16/2017 02:07 PM, Eric S. Raymond wrote: > Daniel J Sebald <dan...@ie...>: >> On 10/16/2017 01:17 PM, Eric S. Raymond wrote: >>> Trial git repo is back up, with the conversion bug I previously noted fixed. >> >> Generally, cloning seems to take longer than I had expected, given gnuplot >> is a rather lean project. It could be that SourceForge is just slow. The >> cloning seems "chunky" in the respect it loads a bunch of objects then sort >> of slows down; speeds up again, slows down. > > There's a pack command that helps with that - I forgot to use it. I'll > do it on the next version; I've added it to the conversion script. > >> I don't see any authorship mapping; everything seems to appear as the >> committer is the author. For example, I've searched "git log" for "Sebald" >> and only see my name appear in ancillary comments. Never is my name/address >> as gotten from the ChangeLog record in the authorship line. > > That's...very odd. I'll look into it. > >> Some entries near the beginning of the project, as viewed through gitg: >> >> # Apr 15 1998, 20:16 Initial import of beta340. >> >> In gitg, no file diffs appear. > > I see it too. Some kind of fluky CVS artifact - probably of no > significance. A pretty common sort of glitch in older repos. Yes, it's as though two entries were made for the same CVS checkin. The above and next entries have the same time stamp. >> # Apr 15 1998, 20:16 *** empty log message *** >> >> In gitg, "Loading diff..." never resolves. > > I see two commits that could match that. They're both huge tree imports; > I'm not surprised your differ does a semi-infinite grind. Oh, sure enough. gitk has no problems with the repo and actually resolves diffs quite quickly compared to gitg, which often displayes "Loading diff..." for five seconds or more. gitg project has switched to gtk3 recently, and it just isn't the same as it once was. The older version was the best at displaying diffs and having a handy window for commit messages that one could edit while staging/de-staging individual hunks. The new version now opens a *modal* commit message window, which is too cumbersome for efficient work. It is "git gui" and "gitk" for me, for now. Dan |