* [Buildroot] [PATCH] .gitignore: Add download directory 'dl'
@ 2009-05-06 22:45 Michael Roth
2009-05-07 3:44 ` Markus Heidelberg
0 siblings, 1 reply; 5+ messages in thread
From: Michael Roth @ 2009-05-06 22:45 UTC (permalink / raw)
To: buildroot
(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
^ permalink raw reply related [flat|nested] 5+ messages in thread
* [Buildroot] [PATCH] .gitignore: Add download directory 'dl'
2009-05-06 22:45 [Buildroot] [PATCH] .gitignore: Add download directory 'dl' Michael Roth
@ 2009-05-07 3:44 ` Markus Heidelberg
2009-05-07 12:21 ` Michael Roth
0 siblings, 1 reply; 5+ messages in thread
From: Markus Heidelberg @ 2009-05-07 3:44 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] [PATCH] .gitignore: Add download directory 'dl'
2009-05-07 3:44 ` Markus Heidelberg
@ 2009-05-07 12:21 ` Michael Roth
2009-05-07 23:44 ` Markus Heidelberg
0 siblings, 1 reply; 5+ messages in thread
From: Michael Roth @ 2009-05-07 12:21 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] [PATCH] .gitignore: Add download directory 'dl'
2009-05-07 12:21 ` Michael Roth
@ 2009-05-07 23:44 ` Markus Heidelberg
2009-05-08 8:22 ` Olaf Rempel
0 siblings, 1 reply; 5+ messages in thread
From: Markus Heidelberg @ 2009-05-07 23:44 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] [PATCH] .gitignore: Add download directory 'dl'
2009-05-07 23:44 ` Markus Heidelberg
@ 2009-05-08 8:22 ` Olaf Rempel
0 siblings, 0 replies; 5+ messages in thread
From: Olaf Rempel @ 2009-05-08 8:22 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-05-08 8:22 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-05-06 22:45 [Buildroot] [PATCH] .gitignore: Add download directory 'dl' Michael Roth
2009-05-07 3:44 ` Markus Heidelberg
2009-05-07 12:21 ` Michael Roth
2009-05-07 23:44 ` Markus Heidelberg
2009-05-08 8:22 ` Olaf Rempel
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.