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: new blktrace release tag?
Date: Mon, 11 May 2009 16:46:47 +0000	[thread overview]
Message-ID: <20090511164647.GE4694@kernel.dk> (raw)
In-Reply-To: <1242043134.4304.31.camel@kitka.ibm.com>

On Mon, May 11 2009, Jens Axboe wrote:
> On Mon, May 11 2009, Eric Sandeen wrote:
> > Jens Axboe wrote:
> > > On Mon, May 11 2009, Martin Peschke wrote:
> > >> 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?
> > > 
> > > Definitely. I'll tag a 1.0.1 right away.
> > 
> > Thanks!
> > 
> > Next time could you keep the tarball snapshot a bit more consistent with
> > previous versions, in particular with a top-level dir?  :)
> > 
> > # tar tvjf blktrace-1.0.1.tar.bz2
> > -rw-rw-r-- root/root       112 2009-05-11 07:00 .gitignore
> > -rw-rw-r-- root/root     18009 2009-05-11 07:00 COPYING
> > -rw-rw-r-- root/root      1992 2009-05-11 07:00 Makefile
> > -rw-rw-r-- root/root      5030 2009-05-11 07:00 README
> > -rw-rw-r-- root/root      1109 2009-05-11 07:00 act_mask.c
> > -rw-rw-r-- root/root      1362 2009-05-11 07:00 barrier.h
> > ...
> 
> Dang, I didn't realize that git archive didn't include a top level dir
> (I just switched my scripts to use that last week). I'll fix that up and
> re-generate the tar balls, thanks for letting me know!

Done, it should be ok now.

-- 
Jens Axboe


  parent reply	other threads:[~2009-05-11 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 11:58 new blktrace release tag? Martin Peschke
2009-05-11 11:59 ` Jens Axboe
2009-05-11 15:58 ` Eric Sandeen
2009-05-11 16:35 ` Jens Axboe
2009-05-11 16:46 ` Jens Axboe [this message]
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=20090511164647.GE4694@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.