From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] misc development news
Date: Fri, 1 May 2009 21:03:22 +0200 [thread overview]
Message-ID: <200905012103.23270.markus.heidelberg@web.de> (raw)
In-Reply-To: <87preu9r1x.fsf@macbook.be.48ers.dk>
Peter Korsgaard, 30.04.2009:
> >>>>> "Markus" == Markus Heidelberg <markus.heidelberg@web.de> writes:
>
> Markus> The problems don't have to be solved, because they don't
> Markus> exist any more, at least not in this amount.
>
> No, not at the moment, but it could happen again. There's also the big
> issue about quality of patches, I certainly think more review would be
> good.
Oh, I meant the problems don't exist in a workflow, where only one
person has commit access and review is done before it. I should have
used "would" to make it clear.
Markus
next prev parent reply other threads:[~2009-05-01 19:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 9:39 [Buildroot] misc development news Peter Korsgaard
2009-02-27 22:05 ` Markus Heidelberg
2009-02-27 23:09 ` Peter Korsgaard
2009-03-31 21:23 ` Peter Korsgaard
2009-04-01 4:47 ` Thiago A. Corrêa
2009-04-28 21:22 ` Peter Korsgaard
2009-04-29 14:58 ` Thiago A. Corrêa
2009-04-29 21:00 ` Markus Heidelberg
2009-04-29 21:17 ` Thiago A. Corrêa
2009-05-01 18:57 ` Markus Heidelberg
2009-04-30 14:03 ` Peter Korsgaard
2009-05-01 19:03 ` Markus Heidelberg [this message]
2009-04-30 13:50 ` Peter Korsgaard
2009-04-06 0:22 ` Thomas Petazzoni
2009-04-06 7:45 ` Peter Korsgaard
2009-04-29 9:44 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2009-04-06 17:13 Darcy Watkins
[not found] <mailman.6835.1239009687.25474.buildroot@busybox.net>
2009-04-06 19:01 ` Frank Hoeflich
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=200905012103.23270.markus.heidelberg@web.de \
--to=markus.heidelberg@web.de \
--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