From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Philipp Stephani Newsgroups: gmane.emacs.devel Subject: Re: Dynamic loading progress Date: Thu, 19 Nov 2015 22:12:14 +0000 Message-ID: References: <83k2ptq5t3.fsf@gnu.org> <87h9kxx60e.fsf@lifelogs.com> <877flswse5.fsf@lifelogs.com> <8737wgw7kf.fsf@lifelogs.com> <87io5bv1it.fsf@lifelogs.com> <87egfzuwca.fsf@lifelogs.com> <876118u6f2.fsf@lifelogs.com> <8737w3qero.fsf@lifelogs.com> <831tbn9g9j.fsf@gnu.org> <878u5upw7o.fsf@lifelogs.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7bb04dc4aea9e80524ec0d50 X-Trace: ger.gmane.org 1447971161 21106 80.91.229.3 (19 Nov 2015 22:12:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Nov 2015 22:12:41 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 19 23:12:36 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZzXRO-0000LK-In for ged-emacs-devel@m.gmane.org; Thu, 19 Nov 2015 23:12:30 +0100 Original-Received: from localhost ([::1]:44253 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzXRO-000892-2A for ged-emacs-devel@m.gmane.org; Thu, 19 Nov 2015 17:12:30 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46802) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzXRK-000889-3S for emacs-devel@gnu.org; Thu, 19 Nov 2015 17:12:26 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZzXRJ-0002pM-65 for emacs-devel@gnu.org; Thu, 19 Nov 2015 17:12:26 -0500 Original-Received: from mail-wm0-x232.google.com ([2a00:1450:400c:c09::232]:33185) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzXRJ-0002pG-0G for emacs-devel@gnu.org; Thu, 19 Nov 2015 17:12:25 -0500 Original-Received: by wmec201 with SMTP id c201so47157299wme.0 for ; Thu, 19 Nov 2015 14:12:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=IYTZjQlTvapIQCanophROpnrSo/UJ9N7zLvAamewdek=; b=MEUerjXzb7ZY90yLFbwPtrVhxquwY09enSuhUYP+DdP1mK6f0sqw3YFn0lJXz4mmTm bI9eauGtC5FIWyOP4lijVsMecOjIt2qAOGH9QDV7UtaE7041ByDJtX9CoDA4h7xgS+W8 JB1jZV6XwsgE8qRZcRC38jUU0eSxWVlFUgPIG/dQth2s7Oq3g/Qe3tbTKR5Ncp/Z3vR2 plz3n0oYZHlGflepfOMIXCRMt1LD6A0y3Vv3mTzSm71h9wywLLVvpxGfe61AxLmnrhQK v0baHdkJOIOUn7ToYt7LUJZayxc1IwZLzo5v2DyOUHKDNkcjwO2shiCmg9W4YXAckOuT sGLA== X-Received: by 10.195.13.135 with SMTP id ey7mr10740011wjd.25.1447971143982; Thu, 19 Nov 2015 14:12:23 -0800 (PST) In-Reply-To: <878u5upw7o.fsf@lifelogs.com> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c09::232 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:194824 Archived-At: --047d7bb04dc4aea9e80524ec0d50 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ted Zlatanov schrieb am Do., 19. Nov. 2015 um 03:19 Uhr: > EZ> Of course! Every feature should be documented, and this one is no > EZ> exception. I suggest to start with NEWS. > > My goal with that question was actually to find out *where* the > developer docs should go, not whether they are necessary. I think we > all agree on the necessity. I can try a first stab at them when I know > in what context they'll exist. > > Regarding NEWS specifically, Aur=C3=A9lien is absent at the moment and wi= ll > be back next week. Maybe Philipp would like to provide the NEWS entries? > I will write them if neither of them is able or if it can't wait until > next week. > I can see whether I can come up with something. However as far as I can see the release of 25.1 is not imminent, so the documentation doesn't need to happen immediately. --047d7bb04dc4aea9e80524ec0d50 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


Ted Zl= atanov <tzz@lifelogs.com> sch= rieb am Do., 19. Nov. 2015 um 03:19=C2=A0Uhr:
EZ> Of course!=C2=A0 Every feature should be documented, and = this one is no
EZ> exception.=C2=A0 I suggest to start with NEWS.

My goal with that question was actually to find out *where* the
developer docs should go, not whether they are necessary.=C2=A0 I think we<= br> all agree on the necessity.=C2=A0 I can try a first stab at them when I kno= w
in what context they'll exist.

Regarding NEWS specifically, Aur=C3=A9lien is absent at the moment and will=
be back next week. Maybe Philipp would like to provide the NEWS entries? I will write them if neither of them is able or if it can't wait until<= br> next week.

I can see whether I can come up with somet= hing. However as far as I can see the release of 25.1 is not imminent, so t= he documentation doesn't need to happen immediately.
--047d7bb04dc4aea9e80524ec0d50--