[Buildroot] [PATCH] .gitignore: Add download directory 'dl'

[Buildroot] [PATCH] .gitignore: Add download directory 'dl'

[Michael Roth]

(And additionally, ease /binaries pattern.)

Signed-off-by: Michael Roth <mroth@nessie.de>
---
 .gitignore |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/.gitignore b/.gitignore
index 4a2de4e..e7117d3 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,7 +1,8 @@
 /build_*
 /project_*
 /toolchain_*
-/binaries/*
+/binaries
+/dl
 /.auto.deps
 /.config.cmd
 /.config.old
-- 
1.6.0.6

[Buildroot] [PATCH] .gitignore: Add download directory 'dl'

[Markus Heidelberg]

Michael Roth, 07.05.2009:
> (And additionally, ease /binaries pattern.)

Yes, the current /binaries/* hid the directory, but completely removed
it by "git-clean -d", which should not be intended.

> Signed-off-by: Michael Roth <mroth@nessie.de>
> ---
>  .gitignore |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/.gitignore b/.gitignore
> index 4a2de4e..e7117d3 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -1,7 +1,8 @@
>  /build_*
>  /project_*
>  /toolchain_*
> -/binaries/*
> +/binaries
> +/dl
>  /.auto.deps
>  /.config.cmd
>  /.config.old

What about additionally adding /.config* ?
I guess it's quite common to have some configs laying around.

Markus

[Buildroot] [PATCH] .gitignore: Add download directory 'dl'

[Michael Roth]

Markus Heidelberg schrieb:

> What about additionally adding /.config* ?
> I guess it's quite common to have some configs laying around.

Hmm, yes, but maybe different people use different names:
For example I'm using config.foobar and you're maybe using
.config.foobar and others maybe using foobar.config etc.

So I don't think, there exists a global rule for custom .config
file names.


Michael

[Buildroot] [PATCH] .gitignore: Add download directory 'dl'

[Markus Heidelberg]

Michael Roth, 07.05.2009:
> Markus Heidelberg schrieb:
> 
> > What about additionally adding /.config* ?
> > I guess it's quite common to have some configs laying around.
> 
> Hmm, yes, but maybe different people use different names:
> For example I'm using config.foobar and you're maybe using
> .config.foobar and others maybe using foobar.config etc.

The Linux Kernel has .* as global ignore rule, which makes .config*
files ignored. Sticking to the already existing .config as prefix for
other configs makes it faster to rename/copy the .config because of the
filename completion.

> So I don't think, there exists a global rule for custom .config
> file names.

Not officially, but maybe as common convention.

If you don't want to add it, it's OK. I will then submit a patch myself,
since I think this is just the most common way to keep backup config
files around.

Markus

[Buildroot] [PATCH] .gitignore: Add download directory 'dl'

[Olaf Rempel]

On Fri, 8 May 2009 01:44:10 +0200
Markus Heidelberg <markus.heidelberg@web.de> wrote:

> Michael Roth, 07.05.2009:
> > Markus Heidelberg schrieb:
> > 
> > > What about additionally adding /.config* ?
> > > I guess it's quite common to have some configs laying around.
> > 
> > Hmm, yes, but maybe different people use different names:
> > For example I'm using config.foobar and you're maybe using
> > .config.foobar and others maybe using foobar.config etc.
> 
> The Linux Kernel has .* as global ignore rule, which makes .config*
> files ignored. Sticking to the already existing .config as prefix for
> other configs makes it faster to rename/copy the .config because of the
> filename completion.
> 
> > So I don't think, there exists a global rule for custom .config
> > file names.
> 
> Not officially, but maybe as common convention.
> 
> If you don't want to add it, it's OK. I will then submit a patch myself,
> since I think this is just the most common way to keep backup config
> files around.
I've added my "personal" configs to .git/info/exclude.
Has the same syntax as .gitignore, but it is not commit to the 
repsitory by accident :)

Regards
Olaf