Lars Gullik Bjønnes | 21 Mar 10:02 2012

[PATCH] Setup .gitignore for generated files


Setting up .gitignore or .git/info/excludes is something that should
be done. Not doing it makes it a lot harder to see actual new files
that should be added.

Signed-off-by: Lars Gullik Bjønnes <larsbj <at> gullik.org>
---
 .gitignore                    |   13 +++++++++++++
 boost/.gitignore              |    1 +
 config/.gitignore             |    6 ++++++
 development/.gitignore        |    1 +
 development/MacOSX/.gitignore |    2 ++
 development/cygwin/.gitignore |    1 +
 lib/.gitignore                |    4 ++++
 lib/lyx2lyx/.gitignore        |    1 +
 po/.gitignore                 |    5 +++++
 sourcedoc/.gitignore          |    1 +
 src/.gitignore                |    6 ++++++
 src/client/.gitignore         |    2 ++
 src/frontends/.gitignore      |    1 +
 src/frontends/qt4/.gitignore  |    5 +++++
 src/support/.gitignore        |    2 ++
 src/tex2lyx/.gitignore        |    2 ++
 16 files changed, 53 insertions(+), 0 deletions(-)
 create mode 100644 .gitignore
 create mode 100644 boost/.gitignore
 create mode 100644 config/.gitignore
 create mode 100644 development/.gitignore
 create mode 100644 development/MacOSX/.gitignore
 create mode 100644 development/cygwin/.gitignore
(Continue reading)

Jean-Marc Lasgouttes | 21 Mar 10:25 2012

Re: [PATCH] Setup .gitignore for generated files

Le 21/03/2012 10:02, Lars Gullik Bjønnes a écrit :
>
> Setting up .gitignore or .git/info/excludes is something that should
> be done. Not doing it makes it a lot harder to see actual new files
> that should be added.

Definitely.

JMarc

Pavel Sanda | 21 Mar 13:13 2012

Re: [PATCH] Setup .gitignore for generated files

Lars Gullik Bj?nnes wrote:
> 
> Setting up .gitignore or .git/info/excludes is something that should
> be done. Not doing it makes it a lot harder to see actual new files
> that should be added.
> 
> Signed-off-by: Lars Gullik Bj?¸nnes <larsbj <at> gullik.org>
> ---
>  .gitignore                    |   13 +++++++++++++

IIRC it's doable through single file, or is such spread intention? P

>  boost/.gitignore              |    1 +
>  config/.gitignore             |    6 ++++++
>  development/.gitignore        |    1 +
>  development/MacOSX/.gitignore |    2 ++
>  development/cygwin/.gitignore |    1 +
>  lib/.gitignore                |    4 ++++
>  lib/lyx2lyx/.gitignore        |    1 +
>  po/.gitignore                 |    5 +++++
>  sourcedoc/.gitignore          |    1 +
>  src/.gitignore                |    6 ++++++
>  src/client/.gitignore         |    2 ++
>  src/frontends/.gitignore      |    1 +
>  src/frontends/qt4/.gitignore  |    5 +++++
>  src/support/.gitignore        |    2 ++
>  src/tex2lyx/.gitignore        |    2 ++
>  16 files changed, 53 insertions(+), 0 deletions(-)
>  create mode 100644 .gitignore
>  create mode 100644 boost/.gitignore
(Continue reading)

Lars Gullik Bjønnes | 22 Mar 02:02 2012

Re: [PATCH] Setup .gitignore for generated files

Pavel Sanda <sanda <at> lyx.org> writes:

| Lars Gullik Bj?nnes wrote:
>> 
>> Setting up .gitignore or .git/info/excludes is something that should
>> be done. Not doing it makes it a lot harder to see actual new files
>> that should be added.
>> 
>> Signed-off-by: Lars Gullik Bj?¸nnes <larsbj <at> gullik.org>
>> ---
>>  .gitignore                    |   13 +++++++++++++
>
| IIRC it's doable through single file, or is such spread intention? P

Yes. It is intentional.

The generic stuff is handled from the top, more specifics, f.ex.
moc_*.cpp is handled where it happens.

If a file suddenly appears in a location where we did not expect we
should now about it.

--

-- 
   Lgb


Gmane