All of 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 20:40:38 +0100	[thread overview]
Message-ID: <007a01c882ec$717efea0$080514ac@atmel.com> (raw)
In-Reply-To: 87skyy2yav.fsf@macbook.be.48ers.dk



>>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
> 
> Ulf> It is not OK, to introduce this without discussing it on the
> Ulf> list though.  Luckily, we have a method to resolve a controversy
> Ulf> and that is to let Eric decide.  I think we should give him
> Ulf> maybe a week, and only if no reply the patches should be
> Ulf> reverted.  (With possible resubmit, if Eric comes back later
> Ulf> with ACK)
> 
> Ulf, you have added plenty of controversal stuff without discussing
> it on the list. 

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


> 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.
> 

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

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

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

> 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.

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

> 
> -- 
> Bye, Peter Korsgaard
>

Best Regards
Ulf Samuelsson 

  parent reply	other threads:[~2008-03-10 19:40 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 [this message]
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='007a01c882ec$717efea0$080514ac@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.