unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: Merging Finder into package mechanism
Date: Mon, 01 Nov 2010 20:58:51 +0200	[thread overview]
Message-ID: <83oca86fbo.fsf@gnu.org> (raw)
In-Reply-To: <C0124917DFC0454FB5F42C56CD90BCD5@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Mon, 1 Nov 2010 10:51:19 -0700
> Cc: emacs-devel@gnu.org
> 
> > > Please keep NEWS updated correctly wrt this breakage.  NEWS is for
> > > users.  If you can update change logs for developers then 
> > > you can also update NEWS for users.  You don't use "placeholders"
> > > in change logs, do you?
> > 
> > I'm not sure you understand how NEWS is supposed to work, or the fact
> > that Emacs 24 is not yet released...
> 
> I'm not sure you understand it.

He does, believe me.

> Nothing, including doc strings, the manuals, and even code behavior, _really_
> matters for users until Emacs is released.  Of course.  But that is no reason to
> wait until just before a release to add the doc strings, update the manual, or
> correct the code.

The reason is insufficient manpower.  Feel free to join the effort of
doing everything in real time, including updating the manuals, if you
can.  If you can't, you will have to live with the fact that docs are
not always in sync with the code, until Emacs is released.

> (I, for one, miss Richard's attention to the doc and NEWS.)

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.



  reply	other threads:[~2010-11-01 18:58 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 [this message]
2010-11-01 22:03             ` Drew Adams
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=83oca86fbo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=drew.adams@oracle.com \
    --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).