Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] CHANGES: add #163 + #473
Date: Fri, 24 Jul 2009 15:02:42 +0200	[thread overview]
Message-ID: <87zlauutcd.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090724110230.3f51597a@surf> (Thomas Petazzoni's message of "Fri\, 24 Jul 2009 11\:02\:30 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

hi,

 Thomas> Le Fri, 24 Jul 2009 07:51:16 +0200,
 Thomas> Peter Korsgaard <jacmet@sunsite.dk> a ?crit :

 >> +	#163: Xtensa architecture port

 Thomas> I might wrong or be missing something, but I haven't seen the
 Thomas> corresponding commits for this (maybe patches too large for
 Thomas> the list ?).

Yes, they are committed and I haven't seen the mails either - seems
like the commit hook has issues when I push multiple changes at once.

(Or it might be something else, I'm having mail and hw problems
today).

 Thomas> But if it was really committed, I was quite worried by the
 Thomas> complexity added by the ? overlay ? mechanism proposed by
 Thomas> this new architecture port, and that a public discussion on
 Thomas> this new mechanism could have been interesting to see if it's
 Thomas> the best solution, if it's the way we want Buildroot to go
 Thomas> forward, etc.

The patches were discussed on the list when they were first submitted,
afaik without much comments. the xtensa people have been asking about
it several times, and I finally promised to commit after 2009.05 was
released:

http://lists.busybox.net/pipermail/buildroot/2009-May/027503.html

I agree that the xtensa stuff is "special" in various ways, but I
think it's more productive to get it into git and then work on getting
it cleaned up more, instead of having it gather dust in bugzilla.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-07-24 13:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24  5:51 [Buildroot] [git commit] CHANGES: add #163 + #473 Peter Korsgaard
2009-07-24  9:02 ` Thomas Petazzoni
2009-07-24 13:02   ` Peter Korsgaard [this message]
2009-07-24 13:35     ` Thomas Petazzoni
2009-07-24 13:46       ` Gustavo Zacarias
2009-07-24 13:52         ` Peter Korsgaard
2009-07-24 13:50       ` Peter Korsgaard
2009-07-24 17:31         ` Maxim Grigoriev
2009-07-24 13:51       ` Marc Gauthier
2009-07-24 13:56         ` Peter Korsgaard
2009-07-24 18:21           ` Maxim Grigoriev
2009-07-25  6:41             ` Peter Korsgaard
2009-07-24 17:29       ` Maxim Grigoriev
2009-07-24 21:54     ` Thomas Petazzoni
2009-07-25  3:22       ` Maxim Grigoriev
2009-07-28  1:48         ` Maxim Grigoriev
2009-07-28 17:42           ` Marc Gauthier

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=87zlauutcd.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