| Message ID | 20171021140108.24066-1-gael.portay@savoirfairelinux.com |
|---|---|
| State | Rejected |
| Headers | show |
| Series | .gitignore: ignore output* | expand |
Hello, On Sat, 21 Oct 2017 10:01:08 -0400, Gaël PORTAY wrote: > 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 <gael.portay@savoirfairelinux.com> > --- > .gitignore | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/.gitignore b/.gitignore > index bb02d9f572..ec5768d053 100644 > --- a/.gitignore > +++ b/.gitignore > @@ -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
On 21-10-17 16:04, Thomas Petazzoni wrote: > Hello, > > On Sat, 21 Oct 2017 10:01:08 -0400, Gaël PORTAY wrote: >> 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 <gael.portay@savoirfairelinux.com> >> --- >> .gitignore | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/.gitignore b/.gitignore >> index bb02d9f572..ec5768d053 100644 >> --- a/.gitignore >> +++ b/.gitignore >> @@ -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 :-) You can also add /output* to .git/info/exclude (this is what I do). Regards, Arnout
Hi Thomas, On Sat, Oct 21, 2017 at 04:04:04PM +0200, Thomas Petazzoni wrote: > Hello, > > On Sat, 21 Oct 2017 10:01:08 -0400, Gaël PORTAY wrote: > > 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 <gael.portay@savoirfairelinux.com> > > --- > > .gitignore | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/.gitignore b/.gitignore > > index bb02d9f572..ec5768d053 100644 > > --- a/.gitignore > > +++ b/.gitignore > > @@ -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. > 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
Hi Arnout, On Sat, Oct 21, 2017 at 08:16:09PM +0200, Arnout Vandecappelle wrote: > > > On 21-10-17 16:04, Thomas Petazzoni wrote: > > Hello, > > > > On Sat, 21 Oct 2017 10:01:08 -0400, Gaël PORTAY wrote: > >> 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 <gael.portay@savoirfairelinux.com> > >> --- > >> .gitignore | 2 +- > >> 1 file changed, 1 insertion(+), 1 deletion(-) > >> > >> diff --git a/.gitignore b/.gitignore > >> index bb02d9f572..ec5768d053 100644 > >> --- a/.gitignore > >> +++ b/.gitignore > >> @@ -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 :-) > > 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
On 22-10-17 00:40, Gaël PORTAY wrote: > Hi Thomas, > > On Sat, Oct 21, 2017 at 04:04:04PM +0200, Thomas Petazzoni wrote: >> Hello, >> >> On Sat, 21 Oct 2017 10:01:08 -0400, Gaël PORTAY wrote: >>> 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 <gael.portay@savoirfairelinux.com> >>> --- >>> .gitignore | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/.gitignore b/.gitignore >>> index bb02d9f572..ec5768d053 100644 >>> --- a/.gitignore >>> +++ b/.gitignore >>> @@ -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. > >> 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. 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
diff --git a/.gitignore b/.gitignore index bb02d9f572..ec5768d053 100644 --- a/.gitignore +++ b/.gitignore @@ -1,4 +1,4 @@ -/output +/output* /dl /.auto.deps /.config.cmd
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 <gael.portay@savoirfairelinux.com> --- .gitignore | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)