From: Eli Zaretskii <eliz@gnu.org>
To: Bastien <bzg@gnu.org>
Cc: Stromeko@nexgo.de, emacs-devel@gnu.org
Subject: Re: Version strings in lisp files?
Date: Sat, 21 Apr 2012 17:14:41 +0300 [thread overview]
Message-ID: <83mx65goj2.fsf@gnu.org> (raw)
In-Reply-To: <878vhpxjhj.fsf@gnu.org>
> From: Bastien <bzg@gnu.org>
> Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-devel@gnu.org
> Date: Sat, 21 Apr 2012 16:11:36 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Achim Gratz <Stromeko@nexgo.de>
> >> Date: Sat, 21 Apr 2012 13:27:48 +0200
> >>
> >> Bastien (the org maintainer) tells me that Emacs requires a version
> >> string to be present in org.el, what's the rationale for that?
> >
> > I don't know why Bastien said that, Lisp files generally don't need
> > any version strings in them. I guess we need to ask Bastien to
> > explain himself.
>
> IIRC, during on of the Org>Emacs merge, I was advised to remove version
> strings from all org*.el/ob*.el files except org.el. Gnus and ERC does
> this too.
>
> So I thought this was related to some policy.
>
> But I'm fine with removing this line if it is not required.
AFAIK, the policy is that _if_ you want some version string in a
package, then keep that to a minimum (1 file). But there's no policy,
AFAIK, to have a version string, if Org doesn't need that.
However, please wait for Stefan and Chong to give you the definitive
word on the current policy.
next prev parent reply other threads:[~2012-04-21 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 11:27 Version strings in lisp files? Achim Gratz
2012-04-21 12:37 ` Jambunathan K
2012-04-21 13:19 ` Bastien
2012-04-21 14:09 ` Jambunathan K
2012-04-21 14:28 ` Bastien
2012-04-21 13:43 ` Eli Zaretskii
2012-04-21 14:11 ` Bastien
2012-04-21 14:14 ` Eli Zaretskii [this message]
2012-04-21 14:34 ` Jambunathan K
2012-04-21 14:48 ` Eli Zaretskii
2012-04-21 14:47 ` Achim Gratz
2012-04-21 19:40 ` Stefan Monnier
2012-04-21 19:54 ` Achim Gratz
2012-04-21 22:59 ` Bastien
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=83mx65goj2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Stromeko@nexgo.de \
--cc=bzg@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).