From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/2] barebox: update the default barebox config name analogous to KERNEL_CONFIG
Date: Tue, 13 Sep 2016 12:54:09 +0200 [thread overview]
Message-ID: <20160913105409.crxd3uzykbwyldeh@pengutronix.de> (raw)
In-Reply-To: <20160913095436.4v62azvr2bl5zacl@pengutronix.de>
On Tue, Sep 13, 2016 at 11:54:36AM +0200, Uwe Kleine-König wrote:
> On Tue, Sep 13, 2016 at 11:21:27AM +0200, Michael Olbrich wrote:
> > I prefer a filename without the version.
>
> I like it with version because this allows to keep the old config
> (similar to the old patch stack, that is versioned, too) for a while
> before/after updating kernel or barebox.
I think keeping the old stuff is really annoying because 'for a while'
means 'forever' in most cases. The end result is, that every kernel and
barebox version ever used in a BSP has a patch stack and config nobody
knows which of those are still needed.
And it's still an option anyways. We're talking about the default value
here and most people don't switch back and forth between versions.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2016-09-13 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 8:04 [ptxdist] [PATCH 1/2] barebox: bump default barebox version Uwe Kleine-König
2016-09-13 8:04 ` [ptxdist] [PATCH 2/2] barebox: update the default barebox config name analogous to KERNEL_CONFIG Uwe Kleine-König
2016-09-13 9:21 ` Michael Olbrich
2016-09-13 9:54 ` Uwe Kleine-König
2016-09-13 10:54 ` Michael Olbrich [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=20160913105409.crxd3uzykbwyldeh@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@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