On Tue, 2012-11-20 at 17:00 +0100, Milan Crha wrote: > Hi, > I'm wondering about usability of git-generated ChangeLog files in > tarball releases. I'd say drop them. Using 'git log' is only one way of tracking historical changes, and it's rarely useful all on its own. This is especially true in a project where changes often aren't always cleanly split into separate commits as is my personal preference, and one commit may cover a *lot* of separate changes. I often find myself using 'git blame', or 'git log -- $FILENAME', or if I *do* use the 'git log' output it'll be coupled with 'git show $COMMIT' to look at individual commits. So having the 'git log' output pre-packaged in a text file doesn't really do much useful for me. What would be *more* useful, perhaps, is publishing a tarball of a '.git' directory which can be extracted into the same location as the tarball, to turn it into a clean checkout of the source tree at the appropriate tag. -- dwmw2
Attachment:
smime.p7s
Description: S/MIME cryptographic signature