From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: commit messages from gforge -> pgsql-committers |
Date: | 2004-05-21 03:47:53 |
Message-ID: | 20040521004642.W5739@ganymede.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 20 May 2004, Bruce Momjian wrote:
> Andrew Dunstan wrote:
> > >>Why would the URL only be temporarily valid?
> > >>
> > >>
> > >
> > >If Marc needed to save disk space or something. If we could
> > >auto-generate on the fly via a URL, even better.
> > >
> >
> > That's what cvsweb does ... it will generate a diff between any 2
> > arbitrary versions of a file on the fly. All you need to know are the
> > revision numbers - e.g.
> > http://developer.postgresql.org/cvsweb.cgi/pgsql-server/configure.diff?r1=1.365&r2=1.366
>
> My point is that for any non-trivial patch, you need to see all the
> files modified in a single view, rather than poke around to see
> different changes made to different files.
I can enable the diff attachment for commit messages ... I just fear the
size of the email going out for some of the large patches that are applied
...
Tom appears to be against, everyone else seems to be for ... should we try
it and see how it works out?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2004-05-21 04:31:20 | Re: commit messages from gforge -> pgsql-committers |
Previous Message | Bruce Momjian | 2004-05-21 03:15:53 | 2-day trip |