Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] .gitignore: ignore outgoing directory
Date: Fri, 11 May 2018 23:06:36 -0300 (BRT)	[thread overview]
Message-ID: <977073365.261665.1526090796931.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <20180428184458.310770ce@windsurf>

> 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

      parent reply	other threads:[~2018-05-12  2:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=977073365.261665.1526090796931.JavaMail.zimbra@datacom.com.br \
    --to=casantos@datacom.ind.br \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox