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 22:35:49 +0100 [thread overview]
Message-ID: <87wsoaz2h6.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <871w6i1d1w.fsf@macbook.be.48ers.dk> (Peter Korsgaard's message of "Mon\, 10 Mar 2008 22\:31\:23 +0100")
>>>>> "Peter" == Peter Korsgaard <jacmet@uclibc.org> writes:
Huh, where did that buildroot at atmel.com come from?
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Peter> Hi,
>>> John certainly seems to be serious about his work.
Ulf> Yes, I agree with this, which is why I recommended he should
Ulf> have write access.
Peter> Ok.
>>> 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> I am talking about sed and awk which will be more difficult.
Peter> Then just do a find ..|xargs on those or use **/*.mk (if you use a
Peter> proper shell).
>>> 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.
Ulf> He complained about things breaking, but this is bound to
Ulf> happen. He seemed to complain a lot on me, when patches in
Ulf> reality came from others. I know *his* patches caused me about
Ulf> 3-4 weeks of extra work.
Peter> Well, it's very hard to be absolutely sure you don't break anything
Peter> when you change something in a system like BR simply because of the
Peter> number of config combinations you would need to test.
Peter> That ofcause doesn't mean we shouldn't be careful, just that random
Peter> breakage is to be expected.
Peter> I've been playing a bit around with buildbot (http://buildbot.net) -
Peter> And that looks quite nice.
Peter> --
Peter> Bye, Peter Korsgaard
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-03-10 21:35 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
[not found] ` <00aa01c882f4$1cfd90f0$080514ac@atmel.com>
[not found] ` <871w6i1d1w.fsf@macbook.be.48ers.dk>
2008-03-10 21:35 ` Peter Korsgaard [this message]
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=87wsoaz2h6.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 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.