From: Jonathan Larmour <jifl@eCosCentric.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: ecos-v3_0-branch
Date: Sun, 22 Feb 2009 21:29:00 -0000 [thread overview]
Message-ID: <49A1C3D0.7000504@eCosCentric.com> (raw)
In-Reply-To: <49A11817.6070006@dallaway.org.uk>
John Dallaway wrote:
>
> I will add some extra components in Bugzilla for the new infrastructure
> packages. Do we really need to split out documentation into separate
> Bugzilla components? Of course, if we did this consistently it would
> double the number of Bugzilla components.
Since not everything has documentation, I wish ;). Personally I would say
not split documentation out separately. It used to be relevant when we had
a separate person dedicated for doing all docs, but not now, nor is it
likely to be the case again.
Jifl
--
*See us at Embedded World 2009, Nürnberg, Germany, 3-5 Mar, Stand 11-300*
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
prev parent reply other threads:[~2009-02-22 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 9:41 ecos-v3_0-branch John Dallaway
2009-02-22 9:17 ` ecos-v3_0-branch John Dallaway
2009-02-22 21:29 ` Jonathan Larmour [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=49A1C3D0.7000504@eCosCentric.com \
--to=jifl@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).