Re: split func.sgml to separated individual sgml files

2025-08-04 Thread Andrew Dunstan
On 2025-07-29 Tu 11:40 AM, Tom Lane wrote: Andrew Dunstan writes: OK. I'm inclined to do this after the CF finishes, to avoid collisions with other patches. I assume it's going to make the CFbot fairly unhappy. +1 for proceeding that way. (I did not look at whether the proposed changes are

Re: split func.sgml to separated individual sgml files

2025-07-29 Thread Tom Lane
Andrew Dunstan writes: > OK. I'm inclined to do this after the CF finishes, to avoid collisions > with other patches. I assume it's going to make the CFbot fairly unhappy. +1 for proceeding that way. (I did not look at whether the proposed changes are sane, but I agree that this'll inevitably b

Re: split func.sgml to separated individual sgml files

2025-07-29 Thread Andrew Dunstan
On 2025-07-29 Tu 2:15 AM, jian he wrote: hi. after run the v2 python script and ``git apply v2-0001-update-filelist.sgml-allfiles.sgml.no-cfbot`` git status -u shows: Changes not staged for commit: (use "git add/rm ..." to update what will be committed) (use "git restore ..." to discard

Re: split func.sgml to separated individual sgml files

2025-07-28 Thread jian he
hi. after run the v2 python script and ``git apply v2-0001-update-filelist.sgml-allfiles.sgml.no-cfbot`` git status -u shows: Changes not staged for commit: (use "git add/rm ..." to update what will be committed) (use "git restore ..." to discard changes in working directory) modified

Re: split func.sgml to separated individual sgml files

2025-06-24 Thread jian he
On Thu, Mar 20, 2025 at 10:16 AM David G. Johnston wrote: > > In short, ready to commit (see last paragraph below however), but the > committer will need to run the python script at the time of commit on the > then-current tree. > hi. more explanation, since the python script seems quite large.

Re: split func.sgml to separated individual sgml files

2025-04-05 Thread David G. Johnston
On Wed, Nov 13, 2024 at 1:11 PM Corey Huinker wrote: > The following is step-by-step logic. >> >> > The end result (one file per section) seems good to me. > > I suspect that reviewer burden may be the biggest barrier to going > forward. Perhaps breaking up the changes so that each new sect1 file

Re: split func.sgml to separated individual sgml files

2024-11-13 Thread Corey Huinker
> > The following is step-by-step logic. > > The end result (one file per section) seems good to me. I suspect that reviewer burden may be the biggest barrier to going forward. Perhaps breaking up the changes so that each new sect1 file gets its own commit, allowing the reviewer to more easily (if