From: John Wiegley <jwiegley@gmail.com>
To: Edward Knyshov <edvorg@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: ChangeLog API
Date: Wed, 23 Mar 2016 11:34:05 -0700 [thread overview]
Message-ID: <m237rh82n6.fsf@newartisans.com> (raw)
In-Reply-To: <CAOi_WG0SAMWj_TXNedZBohC_C+bwcfcaKyEbeGrobvgDh+if9Q@mail.gmail.com> (Edward Knyshov's message of "Sun, 20 Mar 2016 07:19:40 +0000")
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
>>>>> Edward Knyshov <edvorg@gmail.com> writes:
> I just updated 60 elpa packages in my emacs setup and I have no idea what
> changed and what happened to my environment now. I'd like to ask a dev
> community, do we need a some kind of unified changelog api for emacs, so
> each package would provide changes information for each new version via this
> api. I see this feature as ability to read all the changes on all the
> packages after I do such a big upgrade.
Even if we had such an API, enforcing it as a requirement for a package's
inclusion in GNU ELPA -- otherwise, most packages would probably ignore it --
would be rather heavy-weight. Further, the result would likely be a large
volume of information for you to ingest. I don't see the cost/benefit ratio
adding up for an API like this.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]
next prev parent reply other threads:[~2016-03-23 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 7:19 ChangeLog API Edward Knyshov
2016-03-23 18:34 ` John Wiegley [this message]
2016-03-23 18:53 ` Clément Pit--Claudel
2016-03-24 13:29 ` Stefan Monnier
2016-03-24 15:25 ` raman
2016-03-24 15:46 ` Clément Pit--Claudel
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=m237rh82n6.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=edvorg@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.