From: Lucas Stach <l.stach@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: mol@pengutronix.de, barebox@lists.infradead.org, sha@pengutronix.de
Subject: Re: [PATCH] makfiles: add emacs syntax highlighting hint
Date: Thu, 02 Apr 2015 10:55:06 +0200 [thread overview]
Message-ID: <1427964906.24886.14.camel@pengutronix.de> (raw)
In-Reply-To: <20150402083522.GE8125@ns203013.ovh.net>
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.
Or did you mean just moving the rules out of images/, but keeping the
generated binaries there? This might in fact be doable.
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-04-02 8:55 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 [this message]
2015-04-02 8:59 ` Marc Kleine-Budde
2015-04-02 9:23 ` Alexander Aring
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=1427964906.24886.14.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=mol@pengutronix.de \
--cc=plagnioj@jcrosoft.com \
--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