linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Grover <agrover@redhat.com>
To: Jerome Martin <jxm@risingtidesystems.com>
Cc: nab@risingtidesystems.com, Mike Christie <michaelc@cs.wisc.edu>,
	Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
	"Patil, Kiran" <kiran.patil@intel.com>,
	"Love, Robert W" <robert.w.love@intel.com>,
	Madhu Iyengar <madhu.iyengar@qlogic.com>,
	Andrew Vasquez <andrew.vasquez@qlogic.com>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	"J.H." <warthog9@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Matthew Wilcox <matthew@wil.cx>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	linux-iscsi-target-dev <linux-iscsi-target-dev@googlegroups.com>,
	linux-scsi@vger.kernel.org,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Boaz Harrosh <bharrosh@panasas.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Marc Fleischmann <mwf@risingtidesystems.com>
Subject: Re: rtsadmin-v1.99 BETA packages
Date: Tue, 17 May 2011 10:12:12 -0700	[thread overview]
Message-ID: <4DD2AC6C.5020205@redhat.com> (raw)
In-Reply-To: <BANLkTikmp8LdCt2CcpJ21feL8x6=ODGMHQ@mail.gmail.com>

On 05/17/2011 05:56 AM, Jerome Martin wrote:
>   Andy, in your own packaging, I noticed you got rid of the timestamps.
> Please don't, it is here for a good reason: It guarantees a proper
> version comparison/ordering across development builds, for both dpkg and
> rpm. If the version string seems lengthy to you, remember that those are
> just for for development builds, tagged ones will be much easier to the eye.

Sure, I did add a .0 after the 1.99 in order to allow for further
development rpms before 2.0, but I can see how timestamps would be
easier from an automation perspective.

In any case, since my rpm building process is rather manual, I'll
probably refrain from many more versions before release. I just wanted
to get something out there for my own use, and to get it in the pipeline
for distro inclusion.

> Last, but not least regarding your initial question, as Nic said, the
> frozen packages are not part of the OSS tree. In order to differentiate
> the non-OSS tree builds from the OSS ones, we prepend a '1' to the OSS
> tree version strings, allowing us to provide an upgrade path from OSS to
> non OSS (same packages names, but higher version, allows seemless
> upgrade), and also distinguish the packages easily. But please don't
> bother about that specific item, it is not relevant to the OSS branch,
> just mentioning it FYI :-)

Ok, thanks. I think for my purposes, I can ignore the -frozen packages,
and even pretend your non-OSS version doesn't exist, and go from there.

Regards -- Andy

  parent reply	other threads:[~2011-05-17 17:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1304121705.14278.196.camel@haakon2.linux-iscsi.org>
     [not found] ` <1304553788.10072.241.camel@haakon2.linux-iscsi.org>
2011-05-11 16:59   ` rtsadmin-v1.99 BETA packages Andy Grover
2011-05-11 17:36     ` mwf
2011-05-12  0:30     ` Nicholas A. Bellinger
2011-05-12  1:26       ` Andy Grover
2011-05-12  1:56         ` Nicholas A. Bellinger
2011-05-14  1:41       ` Nicholas A. Bellinger
2011-05-14 23:36         ` Andy Grover
2011-05-17  7:30           ` Nicholas A. Bellinger
2011-05-17 17:12             ` Andy Grover
     [not found]             ` <BANLkTikmp8LdCt2CcpJ21feL8x6=ODGMHQ@mail.gmail.com>
2011-05-17 17:12               ` Andy Grover [this message]
2011-07-26 10:29           ` Sangale Harshada Vijay

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=4DD2AC6C.5020205@redhat.com \
    --to=agrover@redhat.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=bharrosh@panasas.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=hpa@zytor.com \
    --cc=jxm@risingtidesystems.com \
    --cc=kiran.patil@intel.com \
    --cc=linux-iscsi-target-dev@googlegroups.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=madhu.iyengar@qlogic.com \
    --cc=matthew@wil.cx \
    --cc=michaelc@cs.wisc.edu \
    --cc=mwf@risingtidesystems.com \
    --cc=nab@risingtidesystems.com \
    --cc=pbonzini@redhat.com \
    --cc=robert.w.love@intel.com \
    --cc=stefanha@gmail.com \
    --cc=warthog9@kernel.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.
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 NNTP newsgroup(s).