public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Repository copyrights updated
Date: Thu, 29 Jan 2009 22:40:00 -0000	[thread overview]
Message-ID: <4982305F.8040503@dallaway.org.uk> (raw)
In-Reply-To: <4981EC0D.2050305@eCosCentric.com>

Hi Jifl

Jonathan Larmour wrote:

> As promised, I have now (finally!) finished updating the copyrights on all
> files. Please let me know about any problems or anomalies. I've looked over
> lots of it, but can't guarantee to have found everything.

Great news! Thanks for all your effort on this.

> After the trunk is unfrozen, there will be a short time to commit anything
> important

It will certainly be worthwhile fixing up the SH3 .ldi files before the
branch is cut. There is also a problem with linking the cxxsupp test for
ARM targets which are still using arm-elf-gcc 3.2.1.

> and then I will cut a branch for the eCos 3.0 release and then I
> will create a first release candidate - there will probably/hopefully only
> be one.

Are you referring to the repository tagging? For avoidance of doubt, I
will be generating the actual releases. I have everything set up for
this on my release machines. Hence my earlier request for shell access
to sourceware.org for uploading of the releases.

John Dallaway

  reply	other threads:[~2009-01-29 22:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 17:49 Jonathan Larmour
2009-01-29 22:40 ` John Dallaway [this message]
2009-01-30  1: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=4982305F.8040503@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --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).