On Thu, Feb 07, 2019 at 12:20:35AM -0500, Tom Lane wrote:
> No, that'd be additional effort on top, which I'm not sure I see
> a reason for. Nobody's given a plausible reason why we need
> a machine-readable way to identify the bug reporter's name from
> the commit log. And we get a fair number o
Nathan Wagner writes:
> On Wed, Feb 06, 2019 at 10:50:51PM -0500, Tom Lane wrote:
>> I do have a modest proposal for improving things going forward. How
>> about, if a commit purports to fix a particular bug, that we say
>> "Fixes: https://postgr.es/m/" in place of our current
>> habit of saying
On Wed, Feb 06, 2019 at 10:50:51PM -0500, Tom Lane wrote:
> Alvaro Herrera writes:
> > On 2019-Feb-06, Tom Lane wrote:
> >> That will have caught exactly none of my own commits.
>
> > Well, what text do you use? I see "Per bug #XYZ" in the free-form text
> > of your commit messages, though that
Michael Paquier writes:
> On Wed, Feb 06, 2019 at 10:50:51PM -0500, Tom Lane wrote:
>> I do have a modest proposal for improving things going forward.
>> How about, if a commit purports to fix a particular bug, that
>> we say "Fixes: https://postgr.es/m/" in place of
>> our current habit of saying
On Wed, Feb 06, 2019 at 10:50:51PM -0500, Tom Lane wrote:
> I do have a modest proposal for improving things going forward.
> How about, if a commit purports to fix a particular bug, that
> we say "Fixes: https://postgr.es/m/" in place of
> our current habit of saying "Discussion: ...". For bugs t
Alvaro Herrera writes:
> On 2019-Feb-06, Tom Lane wrote:
>> That will have caught exactly none of my own commits.
> Well, what text do you use? I see "Per bug #XYZ" in the free-form text
> of your commit messages, though that doesn't explicitly say that the bug
> is fixed. If we agree that that
On 2019-Feb-06, Tom Lane wrote:
> Alvaro Herrera writes:
> > On 2019-Feb-03, Nathan Wagner wrote:
> >> I have used the regex /Fixes bug #([0-9]+)/ to automatically look for
> >> commits purporting to fix bugs by number.
>
> > Let's use that.
>
> That will have caught exactly none of my own comm
Alvaro Herrera writes:
> On 2019-Feb-03, Nathan Wagner wrote:
>> I have used the regex /Fixes bug #([0-9]+)/ to automatically look for
>> commits purporting to fix bugs by number.
> Let's use that.
That will have caught exactly none of my own commits.
regards, tom lane
On 2019-Feb-03, Nathan Wagner wrote:
> If the bug seemed to be either an actual bug or something that would
> have actual work done, I marked these as open. It's entirely probable
> that some or most of these are actually fixed. There were a number
> of cases where committers emailed in a "will
On Thu, Jan 31, 2019 at 08:04:39AM -0300, Alvaro Herrera wrote:
> Here's a bug tracking system that Nathan set up many years ago and
> apparently has kept going unattended. It seems to me that it's
> something that we could base a semi-official bug tracking system on.
>
>
On 2019-Jan-31, Alvaro Herrera wrote:
> Here's a bug tracking system that Nathan set up many years ago and
> apparently has kept going unattended. It seems to me that it's
> something that we could base a semi-official bug tracking system on.
I didn't really remember
Here's a bug tracking system that Nathan set up many years ago and
apparently has kept going unattended. It seems to me that it's
something that we could base a semi-official bug tracking system on.
https://granicus.if.org/pgbugs/
There are clearly things that need fixed, such as
12 matches
Mail list logo
