Additional git conversion steps

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Additional git conversion steps
Дата
Msg-id 19887.1282069302@sss.pgh.pa.us
обсуждение исходный текст
Ответы Re: Additional git conversion steps  (Robert Haas <robertmhaas@gmail.com>)
Re: Additional git conversion steps  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: Additional git conversion steps  (Christopher Browne <cbbrowne@gmail.com>)
Список pgsql-hackers
There are a couple of things I think should happen ASAP once the git
repository is up, but weren't mentioned in Magnus' plans:

1. The various .cvsignore files need to be replaced by .gitignore files.
I am not sure though whether this is a trivial conversion --- does git
have similar default rules about ignoring .o, etc?

2. One thing I will miss from the removal of $PostgreSQL$ tags is that
they guaranteed that every file contained its own full pathname within
the source tree.  I found myself using that an awful lot, mainly as a
source for copying-and-pasting file paths.  To substitute for the tags,
I would like to propose a project standard that every file contain its
pathname in the header comment, not just the bare filename which is the
de facto standard at the moment.  For example, instead of

/*-------------------------------------------------------------------------** plancache.c*      Plan cache management.

we should have

/*-------------------------------------------------------------------------** src/backend/utils/cache/plancache.c*
Plancache management.
 


Whatever we do with the .cvsignore files will need to be back-patched
into all active branches, but I am not so anal-retentive as to wish
to back-patch the pathname comment changes.

Comments?
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Writeable CTEs Desgin Doc on Wiki
Следующее
От: Tom Lane
Дата:
Сообщение: Re: refactoring comment.c