mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Sascha Hauer" <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re[2]: [RFC] Makefile: Create empty <config.h> if this header file is not needed by board
Date: Mon, 11 Mar 2013 20:10:22 +0400	[thread overview]
Message-ID: <1363018222.201808769@f314.mail.ru> (raw)
In-Reply-To: <20130310232442.GX1906@pengutronix.de>

> On Sun, Mar 10, 2013 at 07:01:00PM +0400, Alexander Shiyan wrote:
> > > > > Patch creates empty <config.h> if this header is not needed by board.
> > > > > This will allow to remove many empty config.h files from boards.
> > > 
> > > How does git incorporate with this? I think git just ignores empty files
> > > like these, right?
> > 
> > When I say "empty" here, I mean about not zeroed files, but about
> > files without any content. Now we have 50 config.h files like this.
> 
> My question aimed in the direction whether we end up with empty files
> in git because people accidently add these now generated files.
> 
> I think the goal should be to get rid of the config.h files entirely.
> This patch (or better: the removal of the empty files) could be a good
> start to see what's left.

OK, let's see. I will send the patch again. Second part is a cleanup.

---
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2013-03-11 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 18:30 Alexander Shiyan
2013-03-10 11:08 ` Alexander Shiyan
2013-03-10 14:56   ` Sascha Hauer
2013-03-10 15:01     ` Re[2]: " Alexander Shiyan
2013-03-10 23:24       ` Sascha Hauer
2013-03-11 16:10         ` Alexander Shiyan [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=1363018222.201808769@f314.mail.ru \
    --to=shc_work@mail.ru \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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