The current version of this changelog generation program handles git-note correctly.
If we are going to list all commits, I think it's better to just link to github. I think it supports the same rev list syntax that git cli uses. git-cherry-pick does not automatically copy a git note. I was going to update a program to traverse the cherry pick through the distinctive comment that it leaves. 2013/5/2 Jesse Glick <[email protected]> > On 05/02/2013 01:09 AM, Kohsuke Kawaguchi wrote: > >> I'm not listing every commits in the release. I'm only picking up those >> with the ticket marker. >> > > The problem is that unless git-notes is used to retroactively associate > JIRA IDs, and someone is diligent about doing so, you will then wind up > with a pretty incomplete changelog since lots of important commits are made > without reference to JIRA. (Including many of yours.) My feeling is that > every commit should be included by default and you should have to > explicitly use git-notes to mark it as too trivial to mention. > > (Was there a conclusion as to whether git-cherry-pick correctly picked up > notes from the original commit? Or do these need to be manually copied, if > made prior to the backport?) > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > jenkinsci-dev+unsubscribe@**googlegroups.com<jenkinsci-dev%[email protected]> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > -- Kohsuke Kawaguchi -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
