From: Nick Garnett <nickg@ecoscentric.com>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: [APPROVE?] GNU linkonce patch
Date: Mon, 14 Apr 2003 12:01:00 -0000 [thread overview]
Message-ID: <m37k9xbaho.fsf@miso.calivar.com> (raw)
In-Reply-To: <3E979A44.6060600@eCosCentric.com>
Jonathan Larmour <jifl@eCosCentric.com> writes:
> I won't apply the below patch in deference to Nick applying his linker
> scripts and mine together, which, since they touch the same files, is
> (presumably?) easier overall.
>
> I know he hasn't submitted them for approval yet, but I know he's going to ;).
I was actually waiting for you and Bart to submit your patches for
approval before submitting mine.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
next prev parent reply other threads:[~2003-04-14 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 19:05 Jonathan Larmour
2003-04-09 21:21 ` Gary Thomas
2003-04-12 4:47 ` Jonathan Larmour
2003-04-14 12:01 ` Nick Garnett [this message]
2003-04-14 12:21 ` Jonathan Larmour
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=m37k9xbaho.fsf@miso.calivar.com \
--to=nickg@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.com \
--cc=jifl@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).