On 19.02.2012 16:10, Carlos R. Mafra wrote:
[snip]
I don't have a script to do that, but I've just tried this as a first
order approximation to what people might want:
git log --oneline wmaker-0.92.0+.. |sed 's/^[a-z0-9]* /- /'>
Poor_man_Changelog.txt
See the outcome in
http://www.damtp.cam.ac.uk/user/crm66/Poor_man_Changelog.txt
I must admit: that does not look very nice...
I thought git log would produce something like "hg log --style
changelog" does (from one of my personal projects):
2012-01-21 Andreas Tscharner <[email protected]>
* configure.in, src/Factories.cxx:
Merge with laptop development: bzip compression
[f463ba230247] [tip]
2012-01-18 Andreas Tscharner <[email protected]>
* man/lrc.5, src/example/OSLogos.rif, src/example/logos.rc:
bzip2 compression: Updated examples and documentation
[b533a7e09015]
* src/Factories.cxx, src/compiler/InFileParser.cxx,
src/include/CompressDecompress.hxx:
bzip2 compression: Check for it in input files and create
corresponding classes
[613bf5d95cbd]
How do the Linux Kernel people create their ChangeLogs?
Best regards
Andreas
--
("`-''-/").___..--''"`-._
`o_ o ) `-. ( ).`-.__.`)
(_Y_.)' ._ ) `._ `. ``-..-'
_..`--'_..-_/ /--'_.' .'
(il).-'' (li).' ((!.-'
Andreas Tscharner [email protected] ICQ-No. 14356454
--
To unsubscribe, send mail to [email protected].
