From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Eamon Walsh <ewalsh@tycho.nsa.gov>,
SELinux List <selinux@tycho.nsa.gov>,
Stephen Lawrence <slawrence@tresys.com>
Subject: Re: libselinux version bump past 99
Date: Wed, 09 Mar 2011 10:48:17 -0500 [thread overview]
Message-ID: <4D77A141.6030908@redhat.com> (raw)
In-Reply-To: <1299675962.4884.7.camel@moss-pluto>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/09/2011 08:06 AM, Stephen Smalley wrote:
> On Tue, 2011-03-08 at 17:26 -0500, Eamon Walsh wrote:
>> Libselinux has reached version 2.0.99 and I need to push a bug fix, just checking to make sure 2.0.100 is fine and won't cause any problems e.g. with upgrades.
>
> Shouldn't be a problem. However, it does raise the question of when
> we'll move to 2.1.0. If the version string consists of
> major.minor.revision, then possibly we should be incrementing minor and
> resetting revision whenever there is a new release on
> userspace.selinuxproject.org?
>
Make sense to me.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk13oUEACgkQrlYvE4MpobNdHwCgkTYbCc+K5ese7BudUBVZpkUb
VZ8AoKCPhpN3CoZN/LO1GNR5oJ3SwmSM
=6VnG
-----END PGP SIGNATURE-----
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2011-03-09 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 22:26 libselinux version bump past 99 Eamon Walsh
2011-03-09 13:06 ` Stephen Smalley
2011-03-09 15:48 ` Daniel J Walsh [this message]
2011-03-09 16:02 ` Steve Lawrence
2011-03-09 15:32 ` Daniel J Walsh
2011-03-14 23:26 ` Paul Gortmaker
2011-03-15 11:24 ` Russell Coker
2011-03-15 12:13 ` Stephen Smalley
2011-03-15 12:10 ` Stephen Smalley
2011-03-16 16:04 ` Paul Gortmaker
2011-03-16 16:07 ` Stephen Smalley
2011-03-16 17:59 ` Paul Gortmaker
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=4D77A141.6030908@redhat.com \
--to=dwalsh@redhat.com \
--cc=ewalsh@tycho.nsa.gov \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=slawrence@tresys.com \
/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 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.