All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] .gitignore: remove wrong entries
Date: Sat, 11 Feb 2012 17:12:10 +0100	[thread overview]
Message-ID: <201202111712.10582.arnout@mind.be> (raw)
In-Reply-To: <1328918676-19482-4-git-send-email-felipe.contreras@gmail.com>

On Saturday 11 February 2012 01:04:36 Felipe Contreras wrote:
> These should go into a personal file, like:
> core.excludesfile=/home/felipec/.gitignore
>   .*.sw[nop]
> 
> Some people might prefer to see patches, rejects and other files in the
> output of 'git status' (e.g. me).

 Agreed on most parts, except for the /*.patch.  It was added because git
format-patch creates them.  If they are not ignored, than git add -A won't
work properly anymore.

 While we're talking about gitignore: I have two more things I'd like to
add to it:

/output* (because I often use parallel output dirs within the buildroot
directory, as it gives me access to git).

/defconfig (since it's a generated file).

 What do the others think?


 Regards,
 Arnout


> 
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> ---
>  .gitignore |    7 -------
>  1 files changed, 0 insertions(+), 7 deletions(-)
> 
> diff --git a/.gitignore b/.gitignore
> index 685a9c2..1a7d636 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -5,10 +5,3 @@
>  /.config.old
>  /..config.tmp
>  /.config
> -*.depend
> -*.o
> -/*.patch
> -/*.diff
> -*.orig
> -*.rej
> -*~
> 

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-02-11 16:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-11  0:04 [Buildroot] [PATCH 0/3] Random updates Felipe Contreras
2012-02-11  0:04 ` [Buildroot] [PATCH 1/3] gst-dsp: add dependency to pkg-config Felipe Contreras
2012-02-11 14:42   ` Peter Korsgaard
2012-02-11  0:04 ` [Buildroot] [PATCH 2/3] gst-plugins-base: add option to select 'alsa' Felipe Contreras
2012-02-11 16:05   ` Arnout Vandecappelle
2012-02-11 16:58     ` Peter Korsgaard
2012-02-11  0:04 ` [Buildroot] [PATCH 3/3] .gitignore: remove wrong entries Felipe Contreras
2012-02-11 16:12   ` Arnout Vandecappelle [this message]
2012-02-11 17:27     ` Felipe Contreras
     [not found]   ` <CAAXf6LXsQCsdwswHGa=Ei-+DkB7OyJbKnz7MhatTeEgCk5MMWw@mail.gmail.com>
2012-02-11 23:01     ` Felipe Contreras
2012-02-12 11:05       ` Arnout Vandecappelle
2012-02-13 19:40         ` Felipe Contreras
2012-02-14  9:50       ` Thomas De Schampheleire
     [not found]       ` <CAAXf6LVq7X9-W7syJKUyaz+VyC3+tzGq6A4XMz96ZUqsrR77=w@mail.gmail.com>
2012-02-14 12:37         ` Felipe Contreras

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=201202111712.10582.arnout@mind.be \
    --to=arnout@mind.be \
    --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 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.