mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: mol@pengutronix.de, barebox@lists.infradead.org, sha@pengutronix.de
Subject: Re: [PATCH] makfiles: add emacs syntax highlighting hint
Date: Thu, 2 Apr 2015 11:23:10 +0200	[thread overview]
Message-ID: <20150402092307.GA12759@omega> (raw)
In-Reply-To: <551D04FD.9040106@pengutronix.de>

On Thu, Apr 02, 2015 at 10:59:41AM +0200, Marc Kleine-Budde wrote:
> On 04/02/2015 10:55 AM, Lucas Stach wrote:
> > Am Donnerstag, den 02.04.2015, 10:35 +0200 schrieb Jean-Christophe
> > PLAGNIOL-VILLARD:
> >> On 00:33 Wed 01 Apr     , Marc Kleine-Budde wrote:
> >>> This patches makes a standard emacs to recognise the files as makefiles.
> >> not a fan of vi or emacs stuff in file
> >>
> >> btw I plan to drop the images/ and move them back to the ARCH
> >>
> > I'm not sure if this is time spent well.
> > 
> > Moving the generated images _again_ will get you into some serious
> > discussions with the people integrating barebox into BSP builds. We
> > finally settled for a single directory going forward and changing this
> > is not a good idea.
> 
> +1
> 
> > Or did you mean just moving the rules out of images/, but keeping the
> > generated binaries there? This might in fact be doable.
> 
> On the first sight there's some marvell image related
> doubling/copy-paste leftovers in ARCH and in images/.
> 

reminds me to send patches for RPi build which doesn't place the barebox
image into "images/", otherwise I get a [0]. It's placed in root
directory of barebox "barebox.bin". :-)

- Alex

[0] https://www.mail-archive.com/ptxdist@pengutronix.de/msg09539.html

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

  reply	other threads:[~2015-04-02  9:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 22:33 Marc Kleine-Budde
2015-04-02  8:35 ` Jean-Christophe PLAGNIOL-VILLARD
2015-04-02  8:53   ` Marc Kleine-Budde
2015-04-02  8:57     ` Marc Kleine-Budde
2015-04-02  9:26     ` Jean-Christophe PLAGNIOL-VILLARD
2015-04-02  9:33       ` Marc Kleine-Budde
2015-04-02  8:55   ` Lucas Stach
2015-04-02  8:59     ` Marc Kleine-Budde
2015-04-02  9:23       ` Alexander Aring [this message]
2015-04-02  9:24     ` Jean-Christophe PLAGNIOL-VILLARD

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=20150402092307.GA12759@omega \
    --to=alex.aring@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=mkl@pengutronix.de \
    --cc=mol@pengutronix.de \
    --cc=sha@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