From: Bastien <bzg@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, Stromeko@nexgo.de, emacs-devel@gnu.org
Subject: Re: Version strings in lisp files?
Date: Sun, 22 Apr 2012 00:59:06 +0200 [thread overview]
Message-ID: <87r4vgwv2d.fsf@gnu.org> (raw)
In-Reply-To: <jwvr4vgq3ir.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 21 Apr 2012 15:40:33 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> 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.
>
> Yes, the fewer version numbers (and $Log$-style history) the better.
> That's for "files under revision control". Such data added dynamically
> during the build is perfectly fine, in pretty much any amount.
> We do tolerate a few version tags in a few files because occasionally
> people find it handy, but we definitely do not require them.
Okay, thanks for the explanation.
The latest Org (from git master branch) does not contain the "Version"
string anymore.
--
Bastien
prev parent reply other threads:[~2012-04-21 22:59 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
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 [this message]
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=87r4vgwv2d.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=Stromeko@nexgo.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).