Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package:editors	editors/vi
Date: Mon, 10 Mar 2008 18:14:04 +0100	[thread overview]
Message-ID: <042e01c882d4$d82aa450$f1c4af0a@atmel.com> (raw)
In-Reply-To: 87zlt7bmdg.fsf@macbook.be.48ers.dk

----- Original Message ----- 
From: "Peter Korsgaard" <jacmet@uclibc.org>
To: <buildroot@uclibc.org>
Cc: "Ulf Samuelsson" <ulf.samuelsson@atmel.com>
Sent: Sunday, March 09, 2008 10:47 PM
Subject: Re: [Buildroot] svn commit: trunk/buildroot/package:editors editors/vi


>>>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:
> 
> Hi,
> 
> Hamish> Like Ulf says, it's convenient to be able to grep
> Hamish> package/*/*.mk and now that's broken. I think dividing of the
> Hamish> package/ directory needs discussion first.
> 
> grep -r is your friend.
> 
> I must say I kinda like the splitup of the package dir. The flat tree
> goes back to when we didn't have many packages and no submenus under
> packages. More consistency between menuconfig and the directory
> structure is good thing.
> 
> Hamish> It's not really a crowded directory by modern standards. Our file
> Hamish> systems can cope with much larger directories than that.
> 
> The limiting factor is us humans, not the file systems.
> 

It is not OK, to introduce this without discussing it on the list though.
Luckily, we have a method to resolve a controversy and that is to let Eric decide.
I think we should give him maybe a week, and only if no reply the patches should be reverted.
(With possible resubmit, if Eric comes back later with ACK)

An alternative way of handling the problem is to have TWO trees.

The package tree remains as it is, and then we have a second tree
which contains the configuration files (make & config files) 
and and subdirectories showing the structure of the configuration.
This tree could also contain html documentation of each link.
The second tree would not contain any 




> -- 
> Bye, Peter Korsgaard
>



Best Regards
Ulf Samuelsson

  reply	other threads:[~2008-03-10 17:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07  4:43 [Buildroot] svn commit: trunk/buildroot/package: editors editors/vi Arnar Mar Sig
2008-03-07  7:47 ` [Buildroot] svn commit: trunk/buildroot/package:editors editors/vi Ulf Samuelsson
2008-03-07  8:57   ` Arnar Mar Sig
2008-03-07 10:00     ` Peter Korsgaard
2008-03-07 23:53     ` Hamish Moffatt
2008-03-08  1:57       ` Arnar Mar Sig
2008-03-09 21:47       ` Peter Korsgaard
2008-03-10 17:14         ` Ulf Samuelsson [this message]
2008-03-10 19:07           ` Peter Korsgaard
2008-03-10 19:11             ` sjhill at realitydiluted.com
2008-03-10 19:40             ` Ulf Samuelsson
2008-03-10 20:44               ` Peter Korsgaard
     [not found]                 ` <00aa01c882f4$1cfd90f0$080514ac@atmel.com>
     [not found]                   ` <871w6i1d1w.fsf@macbook.be.48ers.dk>
2008-03-10 21:35                     ` Peter Korsgaard
2008-03-10 21:55                       ` Ulf Samuelsson
2008-03-10 22:53                         ` Peter Korsgaard
2008-03-11 16:32                           ` Arnar Mar Sig

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='042e01c882d4$d82aa450$f1c4af0a@atmel.com' \
    --to=ulf.samuelsson@atmel.com \
    --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