Skip to contentSkip to conversation

.gitignore: Add download directory 'dl'

PATCH New Michael Roth 3 participants 5 messages May 6, 2009 – May 8, 2009

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 .gitignore: Add download directory 'dl'

(And additionally, ease /binaries pattern.)

---
 .gitignore |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
.gitignore +2 -1
index 4a2de4e..e7117d3 100644
@@ -1,7 +1,8 @@
 /build_*
 /project_*
 /toolchain_*
-/binaries/*
+/binaries
+/dl
 /.auto.deps
 /.config.cmd
 /.config.old
Signature · 1 line
1.6.0.6
#1 lore raw

PATCH 1/1 .gitignore: Add download directory 'dl'

Michael Roth, 07.05.2009:

Quoted 1 line

(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.

Quoted 10 lines
---
 .gitignore |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
.gitignore +0 -0
index 4a2de4e..e7117d3 100644

.gitignore line 8

Quoted 9 lines
.gitignore +2 -1
@@ -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

#2 lore raw

PATCH 1/1 .gitignore: Add download directory 'dl'

Quoted 2 lines · Markus Heidelberg

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

#3 lore raw

PATCH 1/1 .gitignore: Add download directory 'dl'

Michael Roth, 07.05.2009:

Quoted 8 lines
Quoted 2 lines · Markus Heidelberg

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.

Quoted 2 lines

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

#4 lore raw

PATCH 1/1 .gitignore: Add download directory 'dl'

Quoted 15 lines · On Fri, 8 May 2009 01:44:10 +0200 Markus Heidelberg <[email protected]>…

Michael Roth, 07.05.2009:

Quoted 8 lines
Quoted 2 lines · Markus Heidelberg

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.

Quoted 8 lines
Quoted 2 lines

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