From: Jonathan Larmour <jifl@eCosCentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: John Dallaway <jld@ecoscentric.com>,
eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: [APPROVE] EB40 RedBoot doc patch for 2.0 branch
Date: Wed, 19 Mar 2003 20:28:00 -0000 [thread overview]
Message-ID: <3E78D255.5090708@eCosCentric.com> (raw)
In-Reply-To: <1048092814.9579.5271.camel@hermes.chez-thomas.org>
Gary Thomas wrote:
> On Wed, 2003-03-19 at 09:32, John Dallaway wrote:
>
>>Name: EB40 RedBoot doc patch
>>
>>Description: Tweaks to the instructions for installing RedBoot on an Atmel
>>AT91EB40 board. The existing instructions are misleading in places and the
>>length of the current ROMRAM images requires that the 'fis write' rune be
>>updated.
>>
>>Rationale: Doc patches are harmless providing they don't introduce build doc
>>errors. Without this patch, installation of RedBoot on the AT91EB40 board
>>according to the instructions will fail.
>>
>>Patch: http://sources.redhat.com/ml/ecos-patches/2003-03/msg00139.html
>
>
> IMO as long as the changes reflect the state of the branch, there
> needs to be no further discussion - certainly not for platform
> details, etc.
In fact, shall we just say that doc patches (like target patches) are exempt?
I'm also beginning to dislike this "voting" thing as such in the sense
that it's very noisy and it's not clear when consensus is reached and it's
okay to apply the patch. I'd prefer it to be "objections only".
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
next prev parent reply other threads:[~2003-03-19 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 16:31 John Dallaway
2003-03-19 16:53 ` Gary Thomas
2003-03-19 20:28 ` Jonathan Larmour [this message]
2003-03-20 1:32 ` Nick Garnett
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=3E78D255.5090708@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.com \
--cc=gary@mlbassoc.com \
--cc=jld@ecoscentric.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).