On 7/1/21 4:29 PM, Peter Eisentraut wrote:
> On 01.07.21 22:22, Andrew Dunstan wrote:
>>
>> On 7/1/21 3:39 PM, Peter Eisentraut wrote:
>>> On 01.07.21 16:47, Andrew Dunstan wrote:
On 6/2/21 4:21 PM, Tom Lane wrote:
> Andrew Dunstan writes:
>> I'm inclined to agree with Alvaro t
On 01.07.21 22:22, Andrew Dunstan wrote:
On 7/1/21 3:39 PM, Peter Eisentraut wrote:
On 01.07.21 16:47, Andrew Dunstan wrote:
On 6/2/21 4:21 PM, Tom Lane wrote:
Andrew Dunstan writes:
I'm inclined to agree with Alvaro that the messages are at best an
oddity. Standard Unix practice is to be
On 7/1/21 3:39 PM, Peter Eisentraut wrote:
> On 01.07.21 16:47, Andrew Dunstan wrote:
>>
>> On 6/2/21 4:21 PM, Tom Lane wrote:
>>> Andrew Dunstan writes:
I'm inclined to agree with Alvaro that the messages are at best an
oddity. Standard Unix practice is to be silent on success.
>>> We
On 01.07.21 16:47, Andrew Dunstan wrote:
On 6/2/21 4:21 PM, Tom Lane wrote:
Andrew Dunstan writes:
I'm inclined to agree with Alvaro that the messages are at best an
oddity. Standard Unix practice is to be silent on success.
We've been steadily moving towards less chatter during builds.
I'd
Andrew Dunstan writes:
>> Shouldn't these new targets be documented somewhere?
> Good point. See attached.
+1, but spell check: "documantation"
regards, tom lane
On 7/1/21 10:50 AM, Tom Lane wrote:
> Andrew Dunstan writes:
>> OK, I think on reflection new targets will be cleaner. What I suggest is
>> the attached, applied to all branches, followed by removal of the four
>> noise messages in just HEAD.
> Shouldn't these new targets be documented somewhere?
Andrew Dunstan writes:
> OK, I think on reflection new targets will be cleaner. What I suggest is
> the attached, applied to all branches, followed by removal of the four
> noise messages in just HEAD.
Shouldn't these new targets be documented somewhere?
regards, tom lane
On 6/2/21 4:21 PM, Tom Lane wrote:
> Andrew Dunstan writes:
>> I'm inclined to agree with Alvaro that the messages are at best an
>> oddity. Standard Unix practice is to be silent on success.
> We've been steadily moving towards less chatter during builds.
> I'd be good with dropping these messag
Andrew Dunstan writes:
> I'm inclined to agree with Alvaro that the messages are at best an
> oddity. Standard Unix practice is to be silent on success.
We've been steadily moving towards less chatter during builds.
I'd be good with dropping these messages in HEAD, but doing so
in the back branch
On 6/1/21 6:23 PM, Tom Lane wrote:
> Peter Eisentraut writes:
>> On 31.05.21 16:16, Andrew Dunstan wrote:
>>> make SKIPDOCS=1 world
>>> make SKIPDOCS=1 install-world
>> Maybe this should be configure option? That's generally where you set
>> what you want to build or not build. (That might al
Peter Eisentraut writes:
> On 31.05.21 16:16, Andrew Dunstan wrote:
>> make SKIPDOCS=1 world
>> make SKIPDOCS=1 install-world
> Maybe this should be configure option? That's generally where you set
> what you want to build or not build. (That might also make the
> buildfarm integration easier
On 31.05.21 16:16, Andrew Dunstan wrote:
make SKIPDOCS=1 world
make SKIPDOCS=1 install-world
Maybe this should be configure option? That's generally where you set
what you want to build or not build. (That might also make the
buildfarm integration easier, since there are already f
On 2021-May-31, Andrew Dunstan wrote:
> However, not all buildfarm animals are set up to build the docs, and not
> all owners necessarily want to. Moreover, we have provision for testing
> various docs formats (PDF, epub etc). So I'd like to be able to build
> and install all the world EXCEPT the
"Joel Jacobson" writes:
> On Mon, May 31, 2021, at 16:16, Andrew Dunstan wrote:
>> However, not all buildfarm animals are set up to build the docs, and not
>> all owners necessarily want to. Moreover, we have provision for testing
>> various docs formats (PDF, epub etc). So I'd like to be able to
On Mon, May 31, 2021, at 16:16, Andrew Dunstan wrote:
> However, not all buildfarm animals are set up to build the docs, and not
> all owners necessarily want to. Moreover, we have provision for testing
> various docs formats (PDF, epub etc). So I'd like to be able to build
> and install all the wo
15 matches
Mail list logo
