View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000681LDMudOtherpublic2009-09-20 15:472010-03-14 09:04
Reporterzesstra Assigned To 
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionduplicate 
Summary0000681: Auto-generate CHANGELOG from commit logs?
DescriptionI often prepare patches for the driver in my local git repository. Once they are finished and tested, I commit them to the driver repository. Sometimes, these series contain more than one patch and/or more than one feature. And usually I am working on more than one local branch.
This leads to the problem, that I can't write any CHANGELOG entries in advance, because I don't know when I will commit to the driver or in which sequence. Additionally, other developers work on the driver and change CHANGELOG. So I change CHANGELOG as short as possible before committing and thats leads to a) I forget thing and b) I have to re-check what I changed in my private commit log.

I think, life could be really easier, if we auto-generate CHANGELOG from the commit messages. This should be fairly simple by using a post-commit hook. I am less confident, that we can exactly reproduce the current format of CHANGELOG, but maybe we can find a solution there.

What do you think about this?
TagsNo tags attached.
External Data (URL)

Relationships

duplicate of 0000723 closedzesstra Generate CHANGELOG from SCM-Changelogs 

Activities

Coogan

2010-03-14 08:30

reporter   ~0001791

I suggest to close this issue because it is handled in 0000723.

zesstra

2010-03-14 09:04

administrator   ~0001792

Ooops. Thank you Coogan. Totally forgot about this one. ;-)

Issue History

Date Modified Username Field Change
2009-09-20 15:47 zesstra New Issue
2010-03-14 08:30 Coogan Note Added: 0001791
2010-03-14 09:03 zesstra Relationship added duplicate of 0000723
2010-03-14 09:04 zesstra Note Added: 0001792
2010-03-14 09:04 zesstra Status new => closed
2010-03-14 09:04 zesstra Resolution open => duplicate