CEPH filesystem development
 help / color / mirror / Atom feed
From: James Page <james.page@ubuntu.com>
To: Sage Weil <sage@inktank.com>
Cc: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Ceph Upstream Tarball + Re: Ceph status for Wheezy
Date: Thu, 12 Jul 2012 11:38:47 +0100	[thread overview]
Message-ID: <4FFEA937.405@ubuntu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1207111553050.693@cobra.newdream.net>

[-- Attachment #1: Type: text/plain, Size: 2015 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/07/12 00:32, Sage Weil wrote:
>> On Wed, 2012-07-11 at 10:01 +0100, James Page wrote:
>>>>> On 11/07/12 01:30, Laszlo Boszormenyi (GCS) wrote:
>>>>>>> You are right, the watch file is outdated.
>>> An updated watch file is attached. Please commit it Sage. It
>>> goes for numbers only, so 0.48argonaut will be 0.48 .
> Why leave off the argonaut?  The intent was to be able to tell from
> e.g. dpkg -l ceph that this was the argonaut stable release,
> without having to figure out through some other channel that 0.48
> is special.
> 

Laszlo - I've updated your watch file and my orig-tar.sh to produce
something that I think works well and automatically - see attached.

Sage - although this technically works with the versioning algorithm in
Debian/Ubuntu I'm uncomfortable using the stable release code name in
the version string.

I would suggest that we document something in debian/NEWS for the 0.48
release version that details that this is the argonaut stable release.


- -- 
James Page
Ubuntu Core Developer
Debian Maintainer
james.page@ubuntu.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJP/qk2AAoJEL/srsug59jDMjcQAIifMFlc8TUMIFPYgMmjYVAb
6mx0cx5pLsmUqGyGSmV+L97+XNDkjABKiudNBFQRsDawbwsYNHNGqH2vNxE6jkEq
e+i3J/RJaJZnigqvVeTAnqQlCxbz6nOulZsVHtPVB2pp6NUN5nN3FXSVpXNMJW3K
NtEsRJvDcK9l7l1MH4gKVefOCKbm8b92d/JWV+HV0rIJBCPx8N/MfQejhCmGNOsy
ykjhdsXodcEXiPWfwIOE+3foS54AXV5mWodY2Fg6P0n6c23NnyN/E9rMMVanInju
VZgEDRC5vbfA5Lnpw9a77X77ppUKuzYUGB6LNMfwfXtXkkCXIkCh9BvngkC/7VHO
FsLf4QKE2y2/VsR36mFt6cQIUW22STtY/tR611Dlv3KjG79Le5Q+AbeX9MP7otcv
WHm50b+HjCxGSnIw8J9Vs1BO5ldjmxyvmdiuxBms+Nud46Ad8ZXT6RGtQEPOkDSj
IYH9bO+2nnchc8Wnv+DKp33eMzB+iwEKsNuuFCClR0lMRAWUnnf6EGLHtAGqRXym
zKfOeon17qsLpS7rWv8b53mKqvuyh1rPC4K2QjEQtTqArj9143B/mbrIpL/QKMjU
JS1IsFlztzJGXRFviMS6ImWZTLY6YQYFtuaZ4obKCQ+NLWqsqtV22GakyQgkE+DY
DCvcoLzC7q5f8wkyn1L5
=LhJK
-----END PGP SIGNATURE-----

[-- Attachment #2: watch --]
[-- Type: text/plain, Size: 97 bytes --]

version=3
https://github.com/ceph/ceph/tags .*/tarball/v(\d[\d\.]+).* debian debian/orig-tar.sh


[-- Attachment #3: orig-tar.sh --]
[-- Type: application/x-shellscript, Size: 294 bytes --]

  reply	other threads:[~2012-07-12 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4FFC44BE.6090505@ubuntu.com>
     [not found] ` <1341966632.12180.22.camel@julia>
     [not found]   ` <4FFD40DA.7020408@ubuntu.com>
2012-07-11 21:43     ` Ceph Upstream Tarball + Re: Ceph status for Wheezy Laszlo Boszormenyi (GCS)
2012-07-11 23:32       ` Sage Weil
2012-07-12 10:38         ` James Page [this message]
2012-07-12 10:38       ` James Page

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=4FFEA937.405@ubuntu.com \
    --to=james.page@ubuntu.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gcs@debian.hu \
    --cc=sage@inktank.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox