long B.K.O entries due to SVN commits

[Arnd Baecker]

Hi,

for some of the entries in the B.K.O,
e.g  http://bugs.kde.org/show_bug.cgi?id=140131,
it is getting quite difficult to keep track of
the opinions posted because of the long parts of svn diffs.

Just wondering whether it would be better
(at least for non-coders like me I think it would ;-)
to just have the message that there is a commit
(and its svn version), without the diff - anyone who is
interested could then just do that diff himself with the usual
svn tools?

The problem is that these long entries make it more likely
that bugs get closed, though there are still open
issues mentioned along the way.

Best, Arnd

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Colin Guthrie-6]

Arnd Baecker wrote:

> for some of the entries in the B.K.O,
> e.g  http://bugs.kde.org/show_bug.cgi?id=140131,
> it is getting quite difficult to keep track of
> the opinions posted because of the long parts of svn diffs.
>
> Just wondering whether it would be better
> (at least for non-coders like me I think it would ;-)
> to just have the message that there is a commit
> (and its svn version), without the diff - anyone who is
> interested could then just do that diff himself with the usual
> svn tools?
>
> The problem is that these long entries make it more likely
> that bugs get closed, though there are still open
> issues mentioned along the way.

I've never liked the full diff in the BKO entry to be honest.

It's a shame KDE's websvn package does not have a changeset viewer like
Trac as that really would be ideal.

For an example see the last comment on:
http://cvs.mythtv.org/trac/ticket/2418

The commiter has closed the bug with their commit message (as we can do
in BKO) but it has automatically added a link to the changeset itself in
the bug report:
http://cvs.mythtv.org/trac/changeset/13224

Obviously I'm not suggesting BKO migrates to Trac as that would just be
silly! But if a similar changeset viewer could be added to
websvn.kde.org then this kind of cross referencing would also work
nicely in BKO/websvn.

My €0.02

Col

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Colin Guthrie-6]

Colin Guthrie wrote:
> Arnd Baecker wrote:
>> for some of the entries in the B.K.O,
>> e.g  http://bugs.kde.org/show_bug.cgi?id=140131,
>> it is getting quite difficult to keep track of
>> the opinions posted because of the long parts of svn diffs.

> But if a similar changeset viewer could be added to
> websvn.kde.org then this kind of cross referencing would also work
> nicely in BKO/websvn.

Actually there is a way - I just didn't look properly.

If comment 36 on the above bug
(http://bugs.kde.org/show_bug.cgi?id=140131#c36) consisted of just the
commit log message and a link to:

http://websvn.kde.org/?view=rev&revision=653197

then I think Bugzilla would be a lot neater.

Can anyone here make this change? Or would it be a matter of emailing
some of the KDE core team directly to get this changed?

Col


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

2007/4/14, Colin Guthrie <[hidden email]>:

Colin Guthrie wrote:
> Arnd Baecker wrote:
>> for some of the entries in the B.K.O,
>> e.g  http://bugs.kde.org/show_bug.cgi?id=140131,
>> it is getting quite difficult to keep track of
>> the opinions posted because of the long parts of svn diffs.

> But if a similar changeset viewer could be added to
> websvn.kde.org then this kind of cross referencing would also work
> nicely in BKO/websvn.

Actually there is a way - I just didn't look properly.

If comment 36 on the above bug
(http://bugs.kde.org/show_bug.cgi?id=140131#c36 ) consisted of just the
commit log message and a link to:

http://websvn.kde.org/?view=rev&revision=653197

then I think Bugzilla would be a lot neater.

Can anyone here make this change? Or would it be a matter of emailing
some of the KDE core team directly to get this changed?

Col

Hi Colin,

Team use the B.K.O tool but not manage config it

The right way is to add a new CCBUGS/BUG tag with commit witch only give a resume without the diff..

Gilles

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel