Re: rpm changelog (was Re: Notice of intent: patching glibc)
Am 07.09.2011 20:00, schrieb Michael Cronenworth: > Genes MailLists on 09/07/2011 12:57 PM wrote: >> Seems pretty useful for users to see what changed - curious why not? > > Users are not programmers. Commits may range from "merge from branch > such-n-such" to "ran indent to clean up formatting" which has extremely > little value to users. +1 from me. Well, it would be convenient to automate the rpm changelog creation in some way. But we need *our* changelog for *our* changes to the package. Most packages ship a NEWS file anyway, which includes the changes to the software itself. Best Regards, Mario -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rpm changelog (was Re: Notice of intent: patching glibc)
Genes MailLists on 09/07/2011 12:57 PM wrote: > Seems pretty useful for users to see what changed - curious why not? Users are not programmers. Commits may range from "merge from branch such-n-such" to "ran indent to clean up formatting" which has extremely little value to users. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rpm changelog (was Re: Notice of intent: patching glibc)
On 09/07/2011 01:50 PM, Michael Cronenworth wrote: > Rich Megginson on 09/07/2011 12:44 PM wrote: >> git log --oneline TAG-OF-PREVIOUS-RELEASE.. | cat >> >> the | cat (or | more) is needed because git log will truncate lines > > This is not what I meant. > > Upstream may have had 20-30 commits inbetween tags. I wouldn't want to > see 20-30 lines of RPM changelog. Seems pretty useful for users to see what changed - curious why not? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rpm changelog (was Re: Notice of intent: patching glibc)
Rich Megginson on 09/07/2011 12:44 PM wrote: > git log --oneline TAG-OF-PREVIOUS-RELEASE.. | cat > > the | cat (or | more) is needed because git log will truncate lines This is not what I meant. Upstream may have had 20-30 commits inbetween tags. I wouldn't want to see 20-30 lines of RPM changelog. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rpm changelog (was Re: Notice of intent: patching glibc)
On 09/07/2011 11:12 AM, Michael Cronenworth wrote: > Genes MailLists wrote: >> Would a git-shortlog suffice for %changelog ? > It would need to be "git-short-shortlog" (hypothetically) as filling a > rpm changelog with hundreds of lines of commits is not very helpful. > > I've always considered the rpm changelog to be a changelog of the spec > itself and a very brief summary of any upstream changes. git log --oneline TAG-OF-PREVIOUS-RELEASE.. | cat the | cat (or | more) is needed because git log will truncate lines -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: rpm changelog (was Re: Notice of intent: patching glibc)
Genes MailLists wrote: > Would a git-shortlog suffice for %changelog ? It would need to be "git-short-shortlog" (hypothetically) as filling a rpm changelog with hundreds of lines of commits is not very helpful. I've always considered the rpm changelog to be a changelog of the spec itself and a very brief summary of any upstream changes. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
