Обсуждение: pgsql: Import pg_bsd_indent sources.
Import pg_bsd_indent sources. This brings in an exact copy of the pg_bsd_indent repo as of commit d301442799cea44e5ccb04331afc537764ec77c5 (2020-12-28). Discussion: https://postgr.es/m/3935719.1675967430@sss.pgh.pa.us Discussion: https://postgr.es/m/20200812223409.6di3y2qsnvynao7a@alap3.anarazel.de Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/4e831f4cee140b004fae44d528d47c284d8ac9eb Modified Files -------------- src/tools/pg_bsd_indent/.gitignore | 10 + src/tools/pg_bsd_indent/Makefile | 35 + src/tools/pg_bsd_indent/README | 100 ++ src/tools/pg_bsd_indent/README.pg_bsd_indent | 30 + src/tools/pg_bsd_indent/args.c | 354 ++++++ src/tools/pg_bsd_indent/err.c | 67 + src/tools/pg_bsd_indent/err.h | 45 + src/tools/pg_bsd_indent/indent.1 | 618 ++++++++++ src/tools/pg_bsd_indent/indent.c | 1279 ++++++++++++++++++++ src/tools/pg_bsd_indent/indent.h | 51 + src/tools/pg_bsd_indent/indent_codes.h | 75 ++ src/tools/pg_bsd_indent/indent_globs.h | 343 ++++++ src/tools/pg_bsd_indent/io.c | 608 ++++++++++ src/tools/pg_bsd_indent/lexi.c | 724 +++++++++++ src/tools/pg_bsd_indent/parse.c | 342 ++++++ src/tools/pg_bsd_indent/pr_comment.c | 358 ++++++ src/tools/pg_bsd_indent/tests/binary.0 | 9 + src/tools/pg_bsd_indent/tests/binary.0.stdout | 11 + src/tools/pg_bsd_indent/tests/comments.0 | 52 + src/tools/pg_bsd_indent/tests/comments.0.stdout | 60 + src/tools/pg_bsd_indent/tests/comments.pro | 1 + src/tools/pg_bsd_indent/tests/cppelsecom.0 | 7 + src/tools/pg_bsd_indent/tests/cppelsecom.0.stdout | 7 + src/tools/pg_bsd_indent/tests/declarations.0 | 79 ++ .../pg_bsd_indent/tests/declarations.0.stdout | 73 ++ src/tools/pg_bsd_indent/tests/elsecomment.0 | 42 + src/tools/pg_bsd_indent/tests/elsecomment.0.stdout | 47 + src/tools/pg_bsd_indent/tests/elsecomment.pro | 1 + src/tools/pg_bsd_indent/tests/enum.0 | 6 + src/tools/pg_bsd_indent/tests/enum.0.stdout | 5 + src/tools/pg_bsd_indent/tests/f_decls.0 | 27 + src/tools/pg_bsd_indent/tests/f_decls.0.stdout | 30 + src/tools/pg_bsd_indent/tests/float.0 | 6 + src/tools/pg_bsd_indent/tests/float.0.stdout | 8 + src/tools/pg_bsd_indent/tests/label.0 | 13 + src/tools/pg_bsd_indent/tests/label.0.stdout | 14 + src/tools/pg_bsd_indent/tests/label.pro | 1 + src/tools/pg_bsd_indent/tests/list_head.0 | 15 + src/tools/pg_bsd_indent/tests/list_head.0.stdout | 13 + src/tools/pg_bsd_indent/tests/nsac.0 | 4 + src/tools/pg_bsd_indent/tests/nsac.0.stdout | 6 + src/tools/pg_bsd_indent/tests/nsac.pro | 1 + src/tools/pg_bsd_indent/tests/offsetof.0 | 5 + src/tools/pg_bsd_indent/tests/offsetof.0.stdout | 7 + src/tools/pg_bsd_indent/tests/parens.0 | 26 + src/tools/pg_bsd_indent/tests/parens.0.stdout | 26 + src/tools/pg_bsd_indent/tests/parens.pro | 1 + src/tools/pg_bsd_indent/tests/sac.0 | 4 + src/tools/pg_bsd_indent/tests/sac.0.stdout | 6 + src/tools/pg_bsd_indent/tests/sac.pro | 1 + src/tools/pg_bsd_indent/tests/struct.0 | 21 + src/tools/pg_bsd_indent/tests/struct.0.stdout | 23 + src/tools/pg_bsd_indent/tests/surplusbad.0 | 9 + src/tools/pg_bsd_indent/tests/surplusbad.0.stdout | 9 + src/tools/pg_bsd_indent/tests/surplusbad.pro | 1 + src/tools/pg_bsd_indent/tests/types_from_file.0 | 3 + .../pg_bsd_indent/tests/types_from_file.0.stdout | 3 + src/tools/pg_bsd_indent/tests/types_from_file.list | 2 + src/tools/pg_bsd_indent/tests/types_from_file.pro | 1 + src/tools/pg_bsd_indent/tests/wchar.0 | 6 + src/tools/pg_bsd_indent/tests/wchar.0.stdout | 6 + 61 files changed, 5737 insertions(+)
On Sun, Feb 12, 2023 at 6:22 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Import pg_bsd_indent sources. > > This brings in an exact copy of the pg_bsd_indent repo as of > commit d301442799cea44e5ccb04331afc537764ec77c5 (2020-12-28). The plan of this import is that the standalone git version is "dead", correct? Given we now have a version in-tree that's newer than the one in that repo? It would perhaps be a good idea to push a README update to the pg_bsd_indent repo that states this? //Magnus
Magnus Hagander <magnus@hagander.net> writes:
> The plan of this import is that the standalone git version is "dead",
> correct? Given we now have a version in-tree that's newer than the one
> in that repo?
Right.
> It would perhaps be a good idea to push a README update to the
> pg_bsd_indent repo that states this?
Good point. We could either do that or just take that repo down.
I'm happy to push such an update if the latter seems bad.
regards, tom lane
On Sat, Apr 22, 2023 at 4:25 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Magnus Hagander <magnus@hagander.net> writes: > > The plan of this import is that the standalone git version is "dead", > > correct? Given we now have a version in-tree that's newer than the one > > in that repo? > > Right. > > > It would perhaps be a good idea to push a README update to the > > pg_bsd_indent repo that states this? > > Good point. We could either do that or just take that repo down. > I'm happy to push such an update if the latter seems bad. I think it's worth doing. If we just zap it we kill history. Not that there's a huge amount of it in there, but there is some and just in case. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
Magnus Hagander <magnus@hagander.net> writes:
> On Sat, Apr 22, 2023 at 4:25 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Magnus Hagander <magnus@hagander.net> writes:
>>> It would perhaps be a good idea to push a README update to the
>>> pg_bsd_indent repo that states this?
>> Good point. We could either do that or just take that repo down.
>> I'm happy to push such an update if the latter seems bad.
> I think it's worth doing. If we just zap it we kill history. Not that
> there's a huge amount of it in there, but there is some and just in
> case.
OK, README update done.
regards, tom lane
On Sun, Apr 23, 2023, 09:39 Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@hagander.net> writes:
> On Sat, Apr 22, 2023 at 4:25 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Magnus Hagander <magnus@hagander.net> writes:
>>> It would perhaps be a good idea to push a README update to the
>>> pg_bsd_indent repo that states this?
>> Good point. We could either do that or just take that repo down.
>> I'm happy to push such an update if the latter seems bad.
> I think it's worth doing. If we just zap it we kill history. Not that
> there's a huge amount of it in there, but there is some and just in
> case.
OK, README update done.
Thanks!
/Magnus