* [Buildroot] [PATCH] .gitignore: ignore output*
@ 2017-10-21 14:01 Gaël PORTAY
2017-10-21 14:04 ` Thomas Petazzoni
0 siblings, 1 reply; 6+ messages in thread
From: Gaël PORTAY @ 2017-10-21 14:01 UTC (permalink / raw)
To: buildroot
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*
/dl
/.auto.deps
/.config.cmd
--
2.14.2
^ permalink raw reply related [flat|nested] 6+ messages in thread
* [Buildroot] [PATCH] .gitignore: ignore output*
2017-10-21 14:01 [Buildroot] [PATCH] .gitignore: ignore output* Gaël PORTAY
@ 2017-10-21 14:04 ` Thomas Petazzoni
2017-10-21 18:16 ` Arnout Vandecappelle
2017-10-21 22:40 ` Gaël PORTAY
0 siblings, 2 replies; 6+ messages in thread
From: Thomas Petazzoni @ 2017-10-21 14:04 UTC (permalink / raw)
To: buildroot
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
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [PATCH] .gitignore: ignore output*
2017-10-21 14:04 ` Thomas Petazzoni
@ 2017-10-21 18:16 ` Arnout Vandecappelle
2017-10-21 22:41 ` Gaël PORTAY
2017-10-21 22:40 ` Gaël PORTAY
1 sibling, 1 reply; 6+ messages in thread
From: Arnout Vandecappelle @ 2017-10-21 18:16 UTC (permalink / raw)
To: buildroot
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
--
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [PATCH] .gitignore: ignore output*
2017-10-21 14:04 ` Thomas Petazzoni
2017-10-21 18:16 ` Arnout Vandecappelle
@ 2017-10-21 22:40 ` Gaël PORTAY
2017-10-22 10:40 ` Arnout Vandecappelle
1 sibling, 1 reply; 6+ messages in thread
From: Gaël PORTAY @ 2017-10-21 22:40 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [PATCH] .gitignore: ignore output*
2017-10-21 18:16 ` Arnout Vandecappelle
@ 2017-10-21 22:41 ` Gaël PORTAY
0 siblings, 0 replies; 6+ messages in thread
From: Gaël PORTAY @ 2017-10-21 22:41 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [PATCH] .gitignore: ignore output*
2017-10-21 22:40 ` Gaël PORTAY
@ 2017-10-22 10:40 ` Arnout Vandecappelle
0 siblings, 0 replies; 6+ messages in thread
From: Arnout Vandecappelle @ 2017-10-22 10:40 UTC (permalink / raw)
To: buildroot
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
--
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-10-22 10:40 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-10-21 14:01 [Buildroot] [PATCH] .gitignore: ignore output* Gaël PORTAY
2017-10-21 14:04 ` Thomas Petazzoni
2017-10-21 18:16 ` Arnout Vandecappelle
2017-10-21 22:41 ` Gaël PORTAY
2017-10-21 22:40 ` Gaël PORTAY
2017-10-22 10:40 ` Arnout Vandecappelle
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.