unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Version strings in lisp files?
Date: Sat, 21 Apr 2012 13:27:48 +0200	[thread overview]
Message-ID: <87fwbxe34b.fsf@Rainer.invalid> (raw)

I've been working on the build system for org and these changes have
just been merged into org.  As part of the cleanup I had removed all
version strings in Git controlled files since they've mostly been a
source for merge conflicts.  Instead, the build system auto-generates
the version string into org-version.el (which is not committed into the
repository), where it can easily be picked up via autoload.  Bastien
(the org maintainer) tells me that Emacs requires a version string to be
present in org.el, what's the rationale for that?  Since those files
will have to transgress into Bzr it would be possible to alter the files
before committing into Bzr, but that doesn't feel right...


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html




             reply	other threads:[~2012-04-21 11:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21 11:27 Achim Gratz [this message]
2012-04-21 12:37 ` Version strings in lisp files? 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

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=87fwbxe34b.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).