From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: [B.A.T.M.A.N.] Clarification of version number in batctl/main.h
Date: Mon, 22 Jun 2009 14:43:34 +0200 [thread overview]
Message-ID: <200906221443.38100.sven.eckelmann@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
Hi,
I just wanted to ask how to interpret the current version number of batctl.
Does it mean that the current version in svn is before or after a possible
0.2-beta release? Is it important for me because debian differentiates between
before and after something. For example 0.2~beta would mean that there is a
beta version before the 0.2 release. So I wanted to know if should call a svn
snapshot of the current batctl 0.2~beta~svn1317 (svn1317 snapshot before a
possible 0.2~beta release) or 0.2~beta+svn1317 (svn1317 snapshot after the
beta phase has started - no beta version will ever be made available or has
been released already).
It seems that the 0.2~beta~svn1317 is the more "correct" version as it has
less extra rules than 0.2~beta+svn1317. For example there must not be an extra
rule for events like the release of 0.3.1 of batman when Simon changed the
version string to 0.3.1 in 1177 which was before the release of 0.3.1 and thus
shouldn't be called 0.3.1+svn1177.
Can this be interpreted the same way for all other on open-mesh.net published
hosted projects? So if I would create a snapshot version of batman it would
have the version number 0.4~beta~svn1309?
Regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next reply other threads:[~2009-06-22 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 12:43 Sven Eckelmann [this message]
2009-06-23 14:34 ` [B.A.T.M.A.N.] Clarification of version number in batctl/main.h Marek Lindner
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=200906221443.38100.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox