From: Martin Peschke <mpeschke@linux.vnet.ibm.com>
To: linux-btrace@vger.kernel.org
Subject: new blktrace release tag?
Date: Mon, 11 May 2009 11:58:53 +0000 [thread overview]
Message-ID: <1242043134.4304.31.camel@kitka.ibm.com> (raw)
Hi Jens,
a lot of fixes have been committed since 1.0.0, a some which are
essential for users, like the sched_setaffinity() patch.
It would be useful to tag a new release, something like 1.0.1?
Thanks,
Martin
next reply other threads:[~2009-05-11 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 11:58 Martin Peschke [this message]
2009-05-11 11:59 ` new blktrace release tag? Jens Axboe
2009-05-11 15:58 ` Eric Sandeen
2009-05-11 16:35 ` Jens Axboe
2009-05-11 16:46 ` Jens Axboe
2009-05-11 18:03 ` Eric Sandeen
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=1242043134.4304.31.camel@kitka.ibm.com \
--to=mpeschke@linux.vnet.ibm.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.