From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] fs/ext2: rename to 'ext' as it can now build ext2/3/4 filesystems
Date: Tue, 19 Feb 2013 21:48:06 +0100 [thread overview]
Message-ID: <87obfgjaih.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <201302191914.43962.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Tue, 19 Feb 2013 19:14:43 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Yann> Peter, Arnout, All,
Yann> On Tuesday 19 February 2013 Peter Korsgaard wrote:
>> >>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
>>
Arnout> On 18/02/13 00:10, Yann E. MORIN wrote:
>> >> Update defconfigs and boards readmes accordingly.
>>
Arnout> I don't really like this. I think it falls in the category "yes it
Arnout> would make things more consistent, but it's major API breakage that
Arnout> may make upgrading unnecessarily difficult". Peter decided to be more
Arnout> careful with that kind of changes, and rightly so.
>>
>> Agreed.
>>
Arnout> This rename is useful, though, and it shouldn't hurt anyone. If
Arnout> anyone is using it, it will be pretty clear what happened, and it wil
Arnout> draw their attention to the new features of genextfs.sh.
>>
>> Agreed.
Yann> OK, I'm puzzled. 8-/
Yann> Peter, you agreed on both points, which are the opposites one of
Yann> the other. What should I conclude about this: do the change, or
Yann> not do the change?
Huh, Arnout's first comment was about the defconfigs /
BR2_TARGET_ROOTFS_EXT{2,} change, which we both dislike - And the 2nd
was about the fs/ renames which should be transparent to the user.
Unless I'm confused, atleast.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-02-19 20:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 23:10 [Buildroot] [pull request 'next'] Pull request for branch yem-ext234 Yann E. MORIN
2013-02-17 23:10 ` [Buildroot] [PATCH 1/4] fs/ext2: enclose the ext2 options in if...endif Yann E. MORIN
2013-02-18 7:30 ` Arnout Vandecappelle
2013-02-17 23:10 ` [Buildroot] [PATCH 2/4] fs/ext2: add ability to build ext3/4 too Yann E. MORIN
2013-02-19 7:04 ` Arnout Vandecappelle
2013-02-19 12:03 ` Peter Korsgaard
2013-02-19 15:33 ` Arnout Vandecappelle
2013-02-19 17:33 ` Yann E. MORIN
2013-02-19 19:01 ` Yann E. MORIN
2013-02-17 23:10 ` [Buildroot] [PATCH 3/4] fs/ext2: rename to 'ext' as it can now build ext2/3/4 filesystems Yann E. MORIN
2013-02-19 7:20 ` Arnout Vandecappelle
2013-02-19 12:41 ` Peter Korsgaard
2013-02-19 18:14 ` Yann E. MORIN
2013-02-19 20:48 ` Peter Korsgaard [this message]
2013-02-21 22:37 ` Yann E. MORIN
2013-02-19 17:54 ` Yann E. MORIN
2013-02-17 23:10 ` [Buildroot] [PATCH 4/4] fs/ext: add support for ext2 rev0 and rev1 Yann E. MORIN
2013-02-19 7:55 ` Arnout Vandecappelle
2013-02-19 18:10 ` Yann E. MORIN
2013-02-19 23:40 ` Arnout Vandecappelle
2013-02-19 23:47 ` Yann E. MORIN
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=87obfgjaih.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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