public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: "eCos Disuss" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] delete athttpd from official eCos repository?
Date: Mon, 16 Jun 2008 14:58:00 -0000	[thread overview]
Message-ID: <c09652430806160758w517070b1na36d139848f9e30e@mail.gmail.com> (raw)
In-Reply-To: <4856752C.2020305@mlbassoc.com>

On Mon, Jun 16, 2008 at 4:14 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> Øyvind Harboe wrote:
>>
>> The athttpd stuff in CVS HEAD is hopelessly out of date.
>>
>> I'd like to see it either deleted from the official repository or
>> brought up to date, I don't care which.
>>
>> The current CVS HEAD athttpd can only give athttpd undeserved flak.
>>
>> The problem is of course that nobody steps up to the plate
>> to do all the work that is required to be able to update
>> athttpd in the official eCos repository.
>>
>> The latest athttpd version is at www.ecosforget.net
>>
>
> If the code is acceptable (and assignable!) for eCos, why not
> just send a patch?  It's not that we're not interested, we
> just can't do all the work (nor can we take responsibility
> for things like the copyright assignments, etc)

Last I heard, it wasn't accepted due to problems with
copyright assignment(some lingering paperwork). I'm
not sure there were any real problems, just a lack
of "someone" to chase down all the nitty gritties.

Breaking all the work done into lots of small patches to
make one patch for each change will not happen I think.

If someone wants to submit a patch and it is accepted,
then that is fine by me, but currently I can't chase this down.

The latest source code is at www.ecosforge.net.

In lieu of somebody stepping up to do the work, it would
be better for athttpd if the outdated copy in the eCos
repository was deleted. Probably better for eCos as well.

-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2008-06-16 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 14:07 Øyvind Harboe
2008-06-16 14:14 ` Gary Thomas
2008-06-16 14:42   ` Andrew Lunn
2008-06-16 14:58   ` Øyvind Harboe [this message]
2008-06-17  6:50 Øyvind Harboe
2008-06-17  8:15 ` Andrew Lunn
2008-06-17  9:35   ` Øyvind Harboe

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=c09652430806160758w517070b1na36d139848f9e30e@mail.gmail.com \
    --to=oyvind.harboe@zylin.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.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).