Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] CHANGES: add #163 + #473
Date: Fri, 24 Jul 2009 23:54:58 +0200	[thread overview]
Message-ID: <20090724235458.3c0eb392@surf> (raw)
In-Reply-To: <87zlauutcd.fsf@macbook.be.48ers.dk>

Le Fri, 24 Jul 2009 15:02:42 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :

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

Wouldn't it be nice to require some documentation together with that
kind of change ?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2009-07-24 21:54 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
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 [this message]
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=20090724235458.3c0eb392@surf \
    --to=thomas.petazzoni@free-electrons.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