Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package:editors	editors/vi
Date: Mon, 10 Mar 2008 21:44:21 +0100	[thread overview]
Message-ID: <87pru21f8a.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <007a01c882ec$717efea0$080514ac@atmel.com> (Ulf Samuelsson's message of "Mon\, 10 Mar 2008 20\:40\:38 +0100")

>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:

Hi,

 >> Ulf, you have added plenty of controversal stuff without discussing
 >> it on the list. 

 Ulf> I started off by giving a description to Eric what I wanted to
 Ulf> do in the beginning and this was acked by him. There has been
 Ulf> protest against several things which he acked.

And that's basically why we lost Bernard.

 >> I really don't see a simple cleanup like this being a big issue.
 >> 

 >> And no - with all respect, considering Eric's lack of involvement the
 >> last few years - I don't see that as being a solution. Most likely he
 >> isn't reading this thread at all.
 >> 

 Ulf> Then we do not have any way to resolve differences.
 Ulf> How do you plan to resolve this - by suggesting your way is the only way?

Simply by looking at the technical pro/cons. If the patch doesn't
cause any regressions, someone is ready to support it and it helps
cleaning stuff up it can go in for me. You have certainly added stuff
I don't need / use, but so what - As long as it doesn't interfere too
much with how I'm using BR it's fine by me.

John certainly seems to be serious about his work.

I think that's basically the only way to do it with a project without
a benevolent dictator.

 >> Do you have any TECHNICAL objections to the patch? If not, I would
 >> suggest we keep it.
 >> 

 Ulf> Yes, it is harder to process the information in each directory
 Ulf> using scripts.  That is enough for me.

Come on, just add -r to your grep. You already need to search
package/, toolchain/ and target/ anyway. That doesn't sound like a
real issue.

 Ulf> An alternative way of handling the problem is to have TWO trees.
 >> 
 >> That seems to me to complicate matters rather than solving any
 >> problems.

 Ulf> This will provide both the current structure and the structure
 Ulf> people want to move to.  If you think it is over complex, I am
 Ulf> happy if the current patches are reverted.

Bernard several times asked you to fork and do the atmel stuff in a
seperate branch. I still don't think that's a good idea considering
the limited amount of BR development ressources we have.

Let's stop coloring the bike shed and move on to bigger stuff.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2008-03-10 20:44 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
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 [this message]
     [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=87pru21f8a.fsf@macbook.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