public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gitignore scripts/ihex2fw
Date: Sat, 20 Jun 2009 18:25:25 +0530	[thread overview]
Message-ID: <1245502525.3042.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20090620124240.GA692@uranus.ravnborg.org>

On Sat, 2009-06-20 at 14:42 +0200, Sam Ravnborg wrote:
> On Wed, Jun 17, 2009 at 02:11:57PM +0530, Jaswinder Singh Rajput wrote:
> > 
> > scripts/ihex2fw is a binary file is suitable candidate for ignore
> > 
> > Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> > ---
> >  .gitignore |    3 +++
> >  1 files changed, 3 insertions(+), 0 deletions(-)
> > 
> > diff --git a/.gitignore b/.gitignore
> > index cecb3b0..cdfb7ce 100644
> > --- a/.gitignore
> > +++ b/.gitignore
> 
> Why not scripts/.gitignore?

[PATCH] gitignore scripts/ihex2fw

scripts/ihex2fw is a binary files should be ignored

Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
---
 scripts/.gitignore |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/scripts/.gitignore b/scripts/.gitignore
index b939fbd..52cab46 100644
--- a/scripts/.gitignore
+++ b/scripts/.gitignore
@@ -7,3 +7,4 @@ pnmtologo
 bin2c
 unifdef
 binoffset
+ihex2fw
-- 
1.6.0.6




  reply	other threads:[~2009-06-20 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17  8:41 [PATCH] gitignore scripts/ihex2fw Jaswinder Singh Rajput
2009-06-20 12:42 ` Sam Ravnborg
2009-06-20 12:55   ` Jaswinder Singh Rajput [this message]
2009-06-26 22:18     ` Sam Ravnborg

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=1245502525.3042.0.camel@localhost.localdomain \
    --to=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=x86@kernel.org \
    /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