From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: RE: Merging Finder into package mechanism
Date: Mon, 1 Nov 2010 15:03:43 -0700 [thread overview]
Message-ID: <57812C1F8FEB4528A65846F19F669142@us.oracle.com> (raw)
In-Reply-To: <83oca86fbo.fsf@gnu.org>
> docs are not always in sync with the code, until Emacs is released.
> We never strayed from what was in place when Richard was the head
> maintainer. You'd see incomplete documentation then as well, because
> few people would write docs together with code.
Of course doc or NEWS can be incomplete during development.
No one claimed otherwise.
I feel that it was a higher priority for Richard. You can disagree.
Placeholders are not how NEWS is _supposed_ to work. Incomplete or inaccurate
NEWS or doc should not be the _aim_, even if some incompleteness or
incorrectness is inevitable. A placeholder is appropriate if it cannot be
avoided.
next prev parent reply other threads:[~2010-11-01 22:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 20:08 Merging Finder into package mechanism Chong Yidong
2010-08-28 20:34 ` Drew Adams
2010-08-28 23:38 ` Juri Linkov
2010-08-29 1:44 ` Chong Yidong
2010-08-31 0:27 ` Juri Linkov
2010-08-31 1:29 ` Chong Yidong
2010-08-31 22:39 ` Juri Linkov
2010-09-01 6:54 ` Stefan Monnier
2010-09-01 22:05 ` Juri Linkov
2010-09-02 7:54 ` Stefan Monnier
2010-09-03 18:30 ` Chong Yidong
2010-09-03 20:45 ` Juri Linkov
2010-08-30 0:46 ` Chong Yidong
2010-08-31 0:27 ` Juri Linkov
2010-08-31 1:42 ` Chong Yidong
2010-08-31 22:43 ` Juri Linkov
2010-10-30 20:59 ` Drew Adams
2010-10-31 0:23 ` Chong Yidong
2010-10-31 22:29 ` Drew Adams
2010-11-01 16:11 ` Chong Yidong
2010-11-01 17:51 ` Drew Adams
2010-11-01 18:58 ` Eli Zaretskii
2010-11-01 22:03 ` Drew Adams [this message]
2010-11-02 3:54 ` Eli Zaretskii
2010-11-01 21:31 ` Chong Yidong
2010-11-01 22:03 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57812C1F8FEB4528A65846F19F669142@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).