public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@ecoscentric.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Global CFLAGS/LDFLAGS and initialisation priority changes
Date: Mon, 19 Jan 2009 13:56:00 -0000	[thread overview]
Message-ID: <pnhc3vz9et.fsf@delenn.bartv.net> (raw)
In-Reply-To: <4964E40D.9030006@dallaway.org.uk> (message from John Dallaway on 	Wed, 07 Jan 2009 17:19:09 +0000)

>>>>> "John" == John Dallaway <john@dallaway.org.uk> writes:

    John> Hi Bart
    John> When do you anticipate getting to the global CFLAGS/LDFLAGS and
    John> initialisation priority changes? I am happy to take on the
    John> CFLAGS/LDFLAGS changes now if your available time is limited.

The situation is the same as before xmas. I cannot check in the big
CFLAGS/LDFLAGS changes at the moment because it would make things even
more difficult for Jifl's big upcoming changes, including the
copyright banners. However I shall be checking in some of my less
intrusive changes over the next few days.

Note that it would be a bad idea for you to work on the CFLAGS/LDFLAGS
at this time. Apart from the duplication of effort, changing well over
a hundred platform HALs with no copyright assignment in place would be
problematical.

Bart

-- 
Bart Veer                                   eCos Configuration Architect
eCosCentric Limited    The eCos experts      http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK.      Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.

      parent reply	other threads:[~2009-01-19 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 17:19 John Dallaway
2009-01-15 16:36 ` John Dallaway
2009-01-19 13:56 ` Bart Veer [this message]

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=pnhc3vz9et.fsf@delenn.bartv.net \
    --to=bartv@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    /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).