On Saturday 24 October 2015 09:49:15 Jérémy Lal wrote:
> i'm now a happy daily user of gitg 3.18 on debian/sid - and couldn't work
> without it.

I'm glad for you but as a daily user of older Gitg-2 I can't use new one 
(3.x) due to 

  * broken/unusable diff view making it impossible to review large diffs 
involving many files.

  * lack of "blame" view.

  * FTBFS of 3.18.0.


> Note the slow loading of large diffs seems to be fixed (2 seconds for a
> very large one).

I'm glad to read that but I'm unable to confirm it because 3.18.0 FTBFS.

3.17.1 is unfortunately up to 15 times slower than Gitg-2 -- when the latter 
takes 1.5 seconds to start, Gitg-3 may initialise for bloody 15(!) seconds.
I just can't stand it but as I've said earlier this is not a blocker as I 
don't expect new Gitg-3 (with all its new dependencies) to work any faster 
(or even at the same speed) as the Gitg-2.


> Please accept help for packaging,

Could you help to fix FTBFS or maybe follow-up with upstream please?


> as i really don't understand why not
> uploading gitg 3.18 to unstable is wrong.

Because it will remove old Gitg-2 which is still more usable than Gitg-3.
I'm nor replacing bad with worse -- not just yet.

You are welcome to work in experimental branch but please do not upload to 
"unstable" yet.


> I'm offering co-maintenance of the package here.

Thank you. I'm entertaining idea of uploading new source package "gitg2" and 
orphan Gitg-3 and its dependencies (or hand 'em over to you). I'll let you 
know when I'll arrive at my decision -- I'm too busy to think about it right 
now so I need to take some time... :(


> If it is so buggy as to not go to testing, migration-blocking bugs can be
> added easily.

This is not the point. We need to preserve Gitg-2 for a time being until 
Gitg-3 is ready.

-- 
Cheers,
 Dmitry Smirnov.

---

Odious ideas are not entitled to hide from criticism behind the human
shield of their believers' feelings.
        -- Richard Stallman

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to