Tom Lane wrote:
> I wrote:
> > So I'd vote for having both --master-only and its inverse
> > --ignore-master, but I'm not sure we need anything more general
> > than that.
>
> On second thought ... one big problem with --master-only is that
> it's useful only to the extent that you trust git_chang
I wrote:
> So I'd vote for having both --master-only and its inverse
> --ignore-master, but I'm not sure we need anything more general
> than that.
On second thought ... one big problem with --master-only is that
it's useful only to the extent that you trust git_changelog to
have matched up master
Robert Haas wrote:
> > Bottom line: ?I need to start the release notes today --- I can hack my
> > own version and we can revisit this later, which I am afraid will be in
> > one year, or we can just add what I have and we can keep hacking on it
> > as needed.
>
> The release note generation is ti
Robert Haas writes:
> No, he wants to exclude things that were back-patched. But I agree
> it's kind of grotty. Imagine you are preparing release notes for a
> minor release. Now you will want all the back-branch commits, but not
> the ones that were only committed to master. I think rather th
On Tue, Mar 15, 2011 at 10:25 AM, Bruce Momjian wrote:
> Robert Haas wrote:
>> On Tue, Mar 15, 2011 at 9:59 AM, Tom Lane wrote:
>> > Bruce Momjian writes:
>> >> I would like to apply the attached patch to git_changelog for use in
>> >> creating the major release notes. ?I specifically added thes
Bruce Momjian wrote:
> Bottom line: I need to start the release notes today --- I can hack my
> own version and we can revisit this later, which I am afraid will be in
> one year, or we can just add what I have and we can keep hacking on it
> as needed.
Oh, one more thing. pgcvslog was added to
Robert Haas wrote:
> On Tue, Mar 15, 2011 at 9:59 AM, Tom Lane wrote:
> > Bruce Momjian writes:
> >> I would like to apply the attached patch to git_changelog for use in
> >> creating the major release notes. ?I specifically added these flags:
> >
> >> ? ? --author-after ?Show author after the co
Tom Lane wrote:
> Bruce Momjian writes:
> > I would like to apply the attached patch to git_changelog for use in
> > creating the major release notes. I specifically added these flags:
>
> > --author-after Show author after the commit
> > --master-only Show commits made exclusively to
On Tue, Mar 15, 2011 at 9:59 AM, Tom Lane wrote:
> Bruce Momjian writes:
>> I would like to apply the attached patch to git_changelog for use in
>> creating the major release notes. I specifically added these flags:
>
>> --author-after Show author after the commit
>> --master-only Sho
Bruce Momjian writes:
> I would like to apply the attached patch to git_changelog for use in
> creating the major release notes. I specifically added these flags:
> --author-after Show author after the commit
> --master-only Show commits made exclusively to the master branch
> --r
I would like to apply the attached patch to git_changelog for use in
creating the major release notes. I specifically added these flags:
--author-after Show author after the commit
--master-only Show commits made exclusively to the master branch
--reverse-order Show commits in reve
11 matches
Mail list logo
