Stop the git abuse
Emanuel Rietveld
codehotter at gmail.com
Mon May 21 12:21:11 UTC 2012
On 05/21/2012 01:56 PM, Ralf Corsepius wrote:
> Technically, the major difference is git recording each and every
> detail, which an rpm's user hardly is interested in. The latter audience
> is not interested in seeing these details, they are interesting in
> "summaries".
>
> E.g. they are not interested in seeing
> ........ ABC-3
> ... Fix memory leak (PR XYZ).
> ... merge from HEAD.
> ... merge cleanup.
> ... fix typo in previous commit.
> ... fix yet another typo.
> ........ ABC-2
> ... Upstream update.
>
> They are interested in reading
> ........ ABC-3
> ... Fix memory leak (PR XYZ).
> ........ ABC-2
> ... Upstream update.
>
> Ralf
Could one of these help?
A) Generate RPM changelog automatically from git, but only process
commit messages with some token, like "%changelog"
B) Have package maintainers use git commit editing tools to make a
'clean history' - squash typo commits, for example, and replace merge
messages with something more informative.
More information about the devel
mailing list