From: | Jimmy Angelakos <vyruss(at)hellug(dot)gr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Erik Wienhold <ewie(at)ewie(dot)name>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, pgsql-www(at)postgresql(dot)org |
Subject: | Re: Diff of this page with other version |
Date: | 2024-03-02 20:28:31 |
Message-ID: | eda40c8d77cf81e098a62ecbca745782@hellug.gr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On 02/03/2024 17:33, Tom Lane wrote:
> Erik Wienhold <ewie(at)ewie(dot)name> writes:
>
>> I think you underestimate the effort because the changes are not always
>> as clear (adding one line) as for copy.sgml as you've shown above. For
>> example, if I check create_table.sgml between v15 and v16, I see that
>> the addition of STORAGE modified an existing line. So that regex has to
>> match and wrap just the relevant substring. When new storage modes are
>> added we end up with nested version info in order to compare vXX with
>> pre v16:
>
> Yeah. I think the chances of getting people to do this in the .sgml
> files are precisely zero. What might have a chance of happening is
> to provide a way on the website of running htmldiff or similar tool
> over two versions of a doc page on-the-fly and show the results.
>
> regards, tom lane
I agree with Tom, I think automation of this process is the way to go
here.
Best regards,
Jimmy
From | Date | Subject | |
---|---|---|---|
Next Message | Marcos Pegoraro | 2024-03-03 14:12:02 | Re: Diff of this page with other version |
Previous Message | Tom Lane | 2024-03-02 17:33:43 | Re: Diff of this page with other version |