public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: NightStrike <nightstrike@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Summer of Code status
Date: Wed, 13 Feb 2008 05:36:00 -0000	[thread overview]
Message-ID: <m37ih9ju4s.fsf@localhost.localdomain> (raw)
In-Reply-To: <b609cb3b0802122101g5f109efeh67a218e2c2120393@mail.gmail.com>

NightStrike <nightstrike@gmail.com> writes:

> > > Project: GCC support for Windows-compatible Structured Exception
> > > Handling (SEH) on the i386 platform
> > > Student: Michele Cicciotti
> > > Mentor: Ian Lance Taylor
> > >
> > >
> > > Any idea what the status is on this?
> >
> > Unfortunately the work was not completed.
> 
> Was it started?  Is there any way for someone to pick up the reins and continue?

Not in any useful way, unfortunately.

Ian

      reply	other threads:[~2008-02-13  5:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 16:53 NightStrike
2008-02-12 23:02 ` Ian Lance Taylor
2008-02-13  5:02   ` NightStrike
2008-02-13  5:36     ` Ian Lance Taylor [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=m37ih9ju4s.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=nightstrike@gmail.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).