From: Jonathan Larmour <jifl@eCosCentric.com>
To: John Dallaway <jld@ecoscentric.com>
Cc: ecos-maintainers@sources.redhat.com
Subject: Re: Proposal for processing patches for the eCos 2.0 branch
Date: Tue, 18 Mar 2003 17:25:00 -0000 [thread overview]
Message-ID: <3E775627.8090803@eCosCentric.com> (raw)
In-Reply-To: <200303181605.21189.jld@ecoscentric.com>
John Dallaway wrote:
>
> The usual procedures for patches to the trunk of the repository would be
> unaffected by all this.
>
> Please comment on or otherwise indicate your acceptance of this proposal
Everything except the 2 day limit. Not everyone can necessarily turn
around replies that quickly if they're out of town. Obviously you're
trying to curtail the patch submission process to prevent everything all
happening at the last minute, but I think that's safe enough because as we
get closer to final, patches will need to be more and more important to
qualify anyway, and the default after all is "no", so it's in people's
interests to get patches in.
Oh, and a cvs diff command to run is as good as a pointer to ecos-patches
IMHO. i.e. "cvs diff -D date1 -D date2 somepackage". It'll be obvious from
the rationale and the date what the ecos-patches message is if anyone's
interested to look at the original. The diff is more useful than the
ecos-patches mail, because many (contributed) patches are changed somewhat
before committing; and sometimes you need multiple patches anyway.
> and
> whether you think configtool patches should be excepted or not.
I don't think I'm qualified to say what should or shouldn't go in the
config tool, and you're the one making the changes, and you're more
cautious than me :-), so I'm happy.
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-18 17:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 8:47 Patches " John Dallaway
2003-03-18 13:48 ` Gary Thomas
2003-03-18 16:04 ` Proposal for processing patches " John Dallaway
2003-03-18 17:25 ` Jonathan Larmour [this message]
2003-03-18 18:21 ` Nick Garnett
2003-03-18 18:56 ` Andrew Lunn
2003-04-12 5:00 ` Jonathan Larmour
2003-04-14 7:28 ` Andrew Lunn
2003-03-18 19:01 ` Andrew Lunn
2003-03-18 22:58 ` Jonathan Larmour
2003-03-18 19:16 ` SNMP for FreeBSD Andrew Lunn
2003-03-19 13:22 ` Jonathan Larmour
2003-03-19 14:23 ` Gary Thomas
2003-03-19 18:07 ` Nick Garnett
2003-03-25 17:01 ` Andrew Lunn
2003-03-19 14:22 ` 2.0 branch: mn10300 debug info patch Bart Veer
2003-03-19 14:40 ` John Dallaway
2003-03-19 18:07 ` Nick Garnett
2003-03-18 18:09 ` Patches for the eCos 2.0 branch Nick Garnett
2003-03-18 18:25 ` Gary Thomas
2003-03-18 19:05 ` Nick Garnett
2003-03-18 19:13 ` Gary Thomas
2003-03-19 10:18 ` New CPM/DPRAM allocator John Dallaway
2003-03-19 13:02 ` Nick Garnett
2003-03-19 14:38 ` Gary Thomas
2003-03-19 15:44 ` John Dallaway
2003-03-19 17:06 ` Gary Thomas
2003-03-19 18:22 ` Nick Garnett
2003-03-19 18:26 ` Gary Thomas
2003-03-19 18:52 ` Nick Garnett
[not found] ` <1048100525.7462.5617.camel@hermes.chez-thomas.org>
2003-03-19 19:21 ` Nick Garnett
2003-03-20 13:02 ` Nick Garnett
2003-03-20 13:14 ` Gary Thomas
2003-03-20 18:11 ` 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=3E775627.8090803@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.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).