Christopher Browne writes:
> You could hide your own favorite patterns by putting this into your
> ~/.gitignore that isn't part of the repo, configuring this globally, thus:
> git config --global core.excludesfile '~/.gitignore'
You can also put per-project setup in .git/info/exclude, works well.
=?ISO-8859-1?Q?Fabr=EDzio_de_Royes_Mello?= writes:
> On Fri, May 24, 2013 at 12:04 AM, Christopher Browne
> wrote:
>> There hasn't been general agreement on the merits of particular .gitignore
>> rules of this sort.
> I agree with you about vim-oriented patterns, because its a particular
> tool,
>"ctags" and "etags" be part of postgres source tree and its generate some
output inside them, so I think we must ignore it.
+1
Regards,
Amul Sul
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/p
On Fri, May 24, 2013 at 12:04 AM, Christopher Browne wrote:
> There hasn't been general agreement on the merits of particular .gitignore
> rules of this sort.
>
> You could hide your own favorite patterns by putting this into your
> ~/.gitignore that isn't part of the repo, configuring this global
There hasn't been general agreement on the merits of particular .gitignore
rules of this sort.
You could hide your own favorite patterns by putting this into your
~/.gitignore that isn't part of the repo, configuring this globally, thus:
git config --global core.excludesfile '~/.gitignore'
That h
Hi all,
The proposed patch add some files to ignore in .gitignore:
- tags (produced by src/tools/make_ctags)
- TAGS (produced bu src/tools/make_etags)
- .*.swp (may appear in source tree if vi/vim was killed by some reason)
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>>
