All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: linux-btrace@vger.kernel.org
Subject: Re: blktrace version number
Date: Wed, 29 Oct 2008 19:25:35 +0000	[thread overview]
Message-ID: <20081029192535.GI31673@kernel.dk> (raw)
In-Reply-To: <20081029154658.GA27173@schmichrtp.de.ibm.com>

On Wed, Oct 29 2008, Alan D. Brunelle wrote:
> Jens Axboe wrote:
> > On Wed, Oct 29 2008, Alan D. Brunelle wrote:
> >> Jens Axboe wrote:
> >>> On Wed, Oct 29 2008, Christof Schmitt wrote:
> >>>> Jens,
> >>>>
> >>>> do you plan to tag a new version in the blktrace git tree?
> >>>>
> >>>> There have been some new features included since version 0.99.3 and
> >>>> from time to time people ask which feature is available in which
> >>>> version. It would be simpler to say "use version 0.99.4" (or whatever
> >>>> the number would be) than "use the latest from the git tree".
> >>> I guess it has been way too long, my intention was to release 1.0
> >>> shortly after that :-)
> >>>
> >>> I'm fine with doing that - Alan, is btt ready for a 1.0 release?
> >>>
> >> Hm, actually, btt is at 2.0.5 - I have updated btrecord/btreplay to
> >> 1.0.0 if you'd like me to push that... :-)
> > 
> > Heh, nevermind the version of the individual packages. To phrase it a
> > bit more clearly, is there anything you feel that needs to be done
> > before I tag the whole repo as 1.0.0?
> > 
> 
> 
> Sure, I think it's probably a good idea...

OK, push any pending updates bits you have today, and I'll tag the repo
as 1.0.0 tomorrow.

-- 
Jens Axboe


      parent reply	other threads:[~2008-10-29 19:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 15:46 blktrace version number Christof Schmitt
2008-10-29 18:31 ` Jens Axboe
2008-10-29 19:04 ` Alan D. Brunelle
2008-10-29 19:11 ` Jens Axboe
2008-10-29 19:22 ` Alan D. Brunelle
2008-10-29 19:25 ` Jens Axboe [this message]

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=20081029192535.GI31673@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-btrace@vger.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 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.