.gitignore: ignore output*
PATCH 1/1 .gitignore: ignore output*
During development, it is often practical to have many output directories. The output directory is easily specified with O=<output> though is it useful to have a convention of 'output...' e.g. "output-rpi", "output-rpi2", and "output-rpi3-64".
--- .gitignore | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
.gitignore +1 -1
@@ -1,4 +1,4 @@ -/output +/output* /dl /.auto.deps /.config.cmd
Signature · 1 line
2.14.2
PATCH 1/1 .gitignore: ignore output*
Hello,
Quoted 15 lines · Ga?l PORTAY
During development, it is often practical to have many output directories. The output directory is easily specified with O=<output> though is it useful to have a convention of 'output...' e.g. "output-rpi", "output-rpi2", and "output-rpi3-64".
Signed-off-by Ga?l PORTAY <[email protected]>--- .gitignore | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-).gitignore +0
-0
.gitignore line 1
Quoted 2 lines
.gitignore +1
-1@@ -1,4 +1,4 @@ -/output +/output*
Not sure this is a good idea, it kind of makes an assumption on how people would name their output directories.
If you're annoyed by your output directories, use make O=../output-rpi2 instead of make O=output-rpi2, and that's it :-)
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 1/1 .gitignore: ignore output*
Quoted 24 lines · Thomas Petazzoni
Hello,
Quoted 15 lines · Ga?l PORTAY
During development, it is often practical to have many output directories. The output directory is easily specified with O=<output> though is it useful to have a convention of 'output...' e.g. "output-rpi", "output-rpi2", and "output-rpi3-64".
Signed-off-by Ga?l PORTAY <[email protected]>--- .gitignore | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-).gitignore +0
-0.gitignore line 1
Quoted 2 lines
.gitignore +1
-1@@ -1,4 +1,4 @@ -/output +/output*Not sure this is a good idea, it kind of makes an assumption on how people would name their output directories.
Quoted 2 lines
If you're annoyed by your output directories, use make O=../output-rpi2 instead of make O=output-rpi2, and that's it :-)
You can also add /output* to .git/info/exclude (this is what I do).
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
PATCH 1/1 .gitignore: ignore output*
Hi Arnout,
Quoted 27 lines · Arnout Vandecappelle
Quoted 24 lines · Thomas Petazzoni
Hello,
Quoted 15 lines · Ga?l PORTAY
During development, it is often practical to have many output directories. The output directory is easily specified with O=<output> though is it useful to have a convention of 'output...' e.g. "output-rpi", "output-rpi2", and "output-rpi3-64".
Signed-off-by Ga?l PORTAY <[email protected]>--- .gitignore | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-).gitignore +0
-0.gitignore line 1
Quoted 2 lines
.gitignore +1
-1@@ -1,4 +1,4 @@ -/output +/output*Not sure this is a good idea, it kind of makes an assumption on how people would name their output directories.
Quoted 5 lines
Quoted 2 lines
If you're annoyed by your output directories, use make O=../output-rpi2 instead of make O=output-rpi2, and that's it :-)
You can also add /output* to .git/info/exclude (this is what I do).
Thanks for this suggestion :) I will look at it.
Regards,
Gael
PATCH 1/1 .gitignore: ignore output*
In reply to Thomas PetazzoniHi Thomas,
Quoted 13 lines · Thomas Petazzoni
Hello,
Quoted 10 lines · Ga?l PORTAY
During development, it is often practical to have many output directories. The output directory is easily specified with O=<output> though is it useful to have a convention of 'output...' e.g. "output-rpi", "output-rpi2", and "output-rpi3-64".
Signed-off-by Ga?l PORTAY <[email protected]>--- .gitignore | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 11 lines
.gitignore line 1
Quoted 7 lines
.gitignore +1
-1@@ -1,4 +1,4 @@ -/output +/output*Not sure this is a good idea, it kind of makes an assumption on how people would name their output directories.
Yes, that is why I mentionned that it should be "useful to have a convention of 'output...'"; and I think that 'output*' is not too intrusive.
Quoted 3 lines
If you're annoyed by your output directories, use make O=../output-rpi2 instead of make O=output-rpi2, and that's it :-)
It is a good suggestion by the way; but I have many buildroot working copies in the same directory, and to avoid collision I prefer having the output directory directly under the working copy.
I will look to the suggestion of Arnout.
King regards,
Gael
PATCH 1/1 .gitignore: ignore output*
Quoted 35 lines · Ga?l PORTAY
Hi Thomas,
Quoted 13 lines · Thomas Petazzoni
Hello,
Quoted 10 lines · Ga?l PORTAY
During development, it is often practical to have many output directories. The output directory is easily specified with O=<output> though is it useful to have a convention of 'output...' e.g. "output-rpi", "output-rpi2", and "output-rpi3-64".
Signed-off-by Ga?l PORTAY <[email protected]>--- .gitignore | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Quoted 11 lines
.gitignore line 1
Quoted 7 lines
.gitignore +1
-1@@ -1,4 +1,4 @@ -/output +/output*Not sure this is a good idea, it kind of makes an assumption on how people would name their output directories.
Yes, that is why I mentionned that it should be "useful to have a convention of 'output...'"; and I think that 'output*' is not too intrusive.
Quoted 3 lines
If you're annoyed by your output directories, use make O=../output-rpi2 instead of make O=output-rpi2, and that's it :-)
Quoted 5 lines
It is a good suggestion by the way; but I have many buildroot working copies in the same directory, and to avoid collision I prefer having the output directory directly under the working copy.
I will look to the suggestion of Arnout.
Actually, what I do is I have an out/ directory with all the build things and I
do builds with O=out/arm-glibc or O=out/rpi0, and I have /out in .git/info/exclude. output is too long :-)
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF