From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Alex Schuilenburg <alexs@ecoscentric.com>,
eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: [ECOS] Re: eCosCentric copyright hold in headers
Date: Thu, 08 Apr 2004 15:27:00 -0000 [thread overview]
Message-ID: <40756F5E.2000407@eCosCentric.com> (raw)
In-Reply-To: <20040408152255.GN29940@lunn.ch>
Andrew Lunn wrote:
> //
> // Maintained by: nickg, dsm
> // Contributors: nickg
> // Derived from:
> // Description: C++ implementation of the C API
> //
> //####DESCRIPTIONEND####
> //
> //==========================================================================
>
> I don't think this is going to be easy. Does dsm maintain this file?
My idea was no he wouldn't... "Maintained by" would be how maintains it
now. Historical info is something for ChangeLogs and cvs logs, not banners,
and not when it's no practical use.
Of course in your example someone would eventually have to clean up that
file (unless the script explicitly watched for user dsm - there aren't that
many names mentioned). There would probably want to also be a NO-MAINTAINER
thing for something which no-one is claiming. That of course will help
people realise where bit-rot is, so this in itself is useful too.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next prev parent reply other threads:[~2004-04-08 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040408101602.GJ29940@lunn.ch>
[not found] ` <4075305D.8020101@eCosCentric.com>
[not found] ` <20040408111939.GK29940@lunn.ch>
[not found] ` <407556D4.8080407@ecoscentric.com>
2004-04-08 14:02 ` Jonathan Larmour
2004-04-08 14:20 ` Andrew Lunn
2004-04-08 14:54 ` Jonathan Larmour
2004-04-08 15:21 ` Andrew Lunn
2004-04-08 15:27 ` Jonathan Larmour [this message]
2004-04-08 14:49 ` Alex Schuilenburg
2004-04-08 15:40 ` Jonathan Larmour
2004-04-08 16:31 ` Alex Schuilenburg
2004-05-07 17:11 Frank Ch. Eigler
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=40756F5E.2000407@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=alexs@ecoscentric.com \
--cc=andrew@lunn.ch \
--cc=ecos-maintainers@ecos.sourceware.org \
/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).