* [Buildroot] [PATCH 1/1] .gitignore: ignore outgoing directory @ 2018-03-08 14:29 Christopher McCrory 2018-04-22 8:05 ` Yann E. MORIN 0 siblings, 1 reply; 6+ messages in thread From: Christopher McCrory @ 2018-03-08 14:29 UTC (permalink / raw) To: buildroot The buildroot documentation for submitting patches creates a new directory "outgoing". This prevents git from nagging about untracked files. Signed-off-by: Christopher McCrory <chrismcc@gmail.com> --- .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index bb02d9f572..f1a065d95e 100644 --- a/.gitignore +++ b/.gitignore @@ -1,5 +1,6 @@ /output /dl +/outgoing /.auto.deps /.config.cmd /.config.old -- 2.14.3 ^ permalink raw reply related [flat|nested] 6+ messages in thread
* [Buildroot] [PATCH 1/1] .gitignore: ignore outgoing directory 2018-03-08 14:29 [Buildroot] [PATCH 1/1] .gitignore: ignore outgoing directory Christopher McCrory @ 2018-04-22 8:05 ` Yann E. MORIN 2018-04-28 16:44 ` Thomas Petazzoni 0 siblings, 1 reply; 6+ messages in thread From: Yann E. MORIN @ 2018-04-22 8:05 UTC (permalink / raw) To: buildroot Christopher, All, On 2018-03-08 06:29 -0800, Christopher McCrory spake thusly: > The buildroot documentation for submitting patches creates a new > directory "outgoing". This prevents git from nagging about untracked > files. > > Signed-off-by: Christopher McCrory <chrismcc@gmail.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Peter, this is a candidate for 2018.02.x as well, I guess. ;-) Regards, Yann E. MORIN. > --- > .gitignore | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/.gitignore b/.gitignore > index bb02d9f572..f1a065d95e 100644 > --- a/.gitignore > +++ b/.gitignore > @@ -1,5 +1,6 @@ > /output > /dl > +/outgoing > /.auto.deps > /.config.cmd > /.config.old > -- > 2.14.3 > > _______________________________________________ > buildroot mailing list > buildroot at busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [PATCH 1/1] .gitignore: ignore outgoing directory 2018-04-22 8:05 ` Yann E. MORIN @ 2018-04-28 16:44 ` Thomas Petazzoni 2018-04-28 16:55 ` Yann E. MORIN 2018-05-12 2:06 ` Carlos Santos 0 siblings, 2 replies; 6+ messages in thread From: Thomas Petazzoni @ 2018-04-28 16:44 UTC (permalink / raw) To: buildroot Hello, On Sun, 22 Apr 2018 10:05:32 +0200, Yann E. MORIN wrote: > Christopher, All, > > On 2018-03-08 06:29 -0800, Christopher McCrory spake thusly: > > The buildroot documentation for submitting patches creates a new > > directory "outgoing". This prevents git from nagging about untracked > > files. > > > > Signed-off-by: Christopher McCrory <chrismcc@gmail.com> > > Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> > > Peter, this is a candidate for 2018.02.x as well, I guess. ;-) I'd like to challenge this patch: I am not super convinced. Creating a outgoing/ directory is not "git format-patch" default behavior. By default, the patches go in the current folder. It's only the Buildroot manual that suggests to put them in an outgoing/ folder (I'm not sure why). My feeling is that the Buildroot manual just gives an example, and really users could put their patches in any other folder, and we're not going to add all random folders in .gitignore. So I would say no to this patch, and therefore disagree with Yann's Acked-by. Peter, Arnout, could you chime in and give your opinion about this ? Best regards, Thomas -- Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [PATCH 1/1] .gitignore: ignore outgoing directory 2018-04-28 16:44 ` Thomas Petazzoni @ 2018-04-28 16:55 ` Yann E. MORIN 2018-04-28 19:49 ` Thomas Petazzoni 2018-05-12 2:06 ` Carlos Santos 1 sibling, 1 reply; 6+ messages in thread From: Yann E. MORIN @ 2018-04-28 16:55 UTC (permalink / raw) To: buildroot Thomas, All, On 2018-04-28 18:44 +0200, Thomas Petazzoni spake thusly: > On Sun, 22 Apr 2018 10:05:32 +0200, Yann E. MORIN wrote: > > Christopher, All, > > > > On 2018-03-08 06:29 -0800, Christopher McCrory spake thusly: > > > The buildroot documentation for submitting patches creates a new > > > directory "outgoing". This prevents git from nagging about untracked > > > files. > > > > > > Signed-off-by: Christopher McCrory <chrismcc@gmail.com> > > > > Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> > > > > Peter, this is a candidate for 2018.02.x as well, I guess. ;-) > > I'd like to challenge this patch: I am not super convinced. Creating a > outgoing/ directory is not "git format-patch" default behavior. By > default, the patches go in the current folder. > > It's only the Buildroot manual that suggests to put them in an > outgoing/ folder (I'm not sure why). And I'm not even sure why we even creat the patches locally, when it is perfectly possible to send them directly, e.g. to send the last three patches: git send-email --to buidlroot at buildroot.org HEAD^^^.. Regards, Yann E. MORIN. > My feeling is that the Buildroot > manual just gives an example, and really users could put their patches > in any other folder, and we're not going to add all random folders > in .gitignore. > > So I would say no to this patch, and therefore disagree with Yann's > Acked-by. Peter, Arnout, could you chime in and give your opinion about > this ? > > Best regards, > > Thomas > -- > Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) > Embedded Linux and Kernel engineering > https://bootlin.com -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [PATCH 1/1] .gitignore: ignore outgoing directory 2018-04-28 16:55 ` Yann E. MORIN @ 2018-04-28 19:49 ` Thomas Petazzoni 0 siblings, 0 replies; 6+ messages in thread From: Thomas Petazzoni @ 2018-04-28 19:49 UTC (permalink / raw) To: buildroot Hello, On Sat, 28 Apr 2018 18:55:22 +0200, Yann E. MORIN wrote: > > It's only the Buildroot manual that suggests to put them in an > > outgoing/ folder (I'm not sure why). > > And I'm not even sure why we even creat the patches locally, when it is > perfectly possible to send them directly, e.g. to send the last three > patches: > > git send-email --to buidlroot at buildroot.org HEAD^^^.. I think for people beginning with git and patches, it is good to use format-patch, so that you can check what the patches look like before sending them. Best regards, Thomas -- Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [PATCH 1/1] .gitignore: ignore outgoing directory 2018-04-28 16:44 ` Thomas Petazzoni 2018-04-28 16:55 ` Yann E. MORIN @ 2018-05-12 2:06 ` Carlos Santos 1 sibling, 0 replies; 6+ messages in thread From: Carlos Santos @ 2018-05-12 2:06 UTC (permalink / raw) To: buildroot > From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com> > To: "Yann Morin" <yann.morin.1998@free.fr>, "Christopher McCrory" <chrismcc@gmail.com> > Cc: "buildroot" <buildroot@buildroot.org> > Sent: Saturday, April 28, 2018 1:44:58 PM > Subject: Re: [Buildroot] [PATCH 1/1] .gitignore: ignore outgoing directory > Hello, > > On Sun, 22 Apr 2018 10:05:32 +0200, Yann E. MORIN wrote: >> Christopher, All, >> >> On 2018-03-08 06:29 -0800, Christopher McCrory spake thusly: >> > The buildroot documentation for submitting patches creates a new >> > directory "outgoing". This prevents git from nagging about untracked >> > files. >> > >> > Signed-off-by: Christopher McCrory <chrismcc@gmail.com> >> >> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> >> >> Peter, this is a candidate for 2018.02.x as well, I guess. ;-) > > I'd like to challenge this patch: I am not super convinced. Creating a > outgoing/ directory is not "git format-patch" default behavior. By > default, the patches go in the current folder. > > It's only the Buildroot manual that suggests to put them in an > outgoing/ folder (I'm not sure why). My feeling is that the Buildroot > manual just gives an example, and really users could put their patches > in any other folder, and we're not going to add all random folders > in .gitignore. > > So I would say no to this patch, and therefore disagree with Yann's > Acked-by. Peter, Arnout, could you chime in and give your opinion about > this ? > > Best regards, If you want to ignore patches under outgoing/ then put something like this in ~/.gitconfig: [core] excludesFile = ~/.gitignore-global And this in ~/.gitignore-global: outgoing/*.patch outgoing/*/*.patch -- Carlos Santos (Casantos) - DATACOM, P&D ?Marched towards the enemy, spear upright, armed with the certainty that only the ignorant can have.? ? Epitaph of a volunteer ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2018-05-12 2:06 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2018-03-08 14:29 [Buildroot] [PATCH 1/1] .gitignore: ignore outgoing directory Christopher McCrory 2018-04-22 8:05 ` Yann E. MORIN 2018-04-28 16:44 ` Thomas Petazzoni 2018-04-28 16:55 ` Yann E. MORIN 2018-04-28 19:49 ` Thomas Petazzoni 2018-05-12 2:06 ` Carlos Santos
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox