Hi,
A very good practice for all developers would be to use the KDE Git
Commit Template
http://techbase.kde.org/Development/Git/Configuration#Commit_Template
and to fill in there all the appropriate fields including FIXED-IN
whenever you commit.
Best regards,
Anne-Marie
On 05/16/2012 05:18 PM, Aleix Pol wrote:
On Wed, May 16, 2012 at 1:46 PM, Aaron J. Seigo<ase...@kde.org> wrote:
On Wednesday, May 16, 2012 13:28:55 Aleix Pol wrote:
In git you know if a bug it's fixed in a release because the release
log contains the bug fix. That is:
git log KDE/4.8..KDE/4.9 | grep "BUG:<id>"
very few of our users will, or even know how, to do this. everyone who reports
a bug, however, knows how to check the bug reports, and that is where this tag
ends up feeding into.
--
Aaron J. Seigo
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Well, it's not about people doing this, but that we're asking people
to put redundant information in the commit message.
Maybe this information could be gathered in a commit hook?
Aleix
_______________________________________________
Bugsquad mailing list
bugsq...@kde.org
https://mail.kde.org/mailman/listinfo/bugsquad
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
