public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Alex Elder <aelder@sgi.com>
Cc: Nathan Scott <nathans@debian.org>, xfs@oss.sgi.com
Subject: Re: User Space Releases
Date: Fri, 4 Dec 2009 11:14:26 -0500	[thread overview]
Message-ID: <20091204161426.GA21499@infradead.org> (raw)
In-Reply-To: <1AB9A794DBDDF54A8A81BE2296F7BDFE83AF34@cf--amer001e--3.americas.sgi.com>

So I think we're almost reading to get xfsprogs 3.1.0 and xfsdump 3.0.4
out of the door.

As far as I'm concerned this is the todo list:

xfsprogs:
 - get my pending repair btree checking patches reviewed and in
 - update the changelog and possibly any other documentation
 - update the Debian packaging

xfsdump:
 - get my configure defaults patch (just posted) in
 - update the changelog and possibly any other documentation
 - update the Debian packaging, possibly including the new source
   generation using the hardlinked package directory.

Nathan, what's the time frame to get the Debian release bits done?

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-12-04 16:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 22:56 User Space Releases Alex Elder
2009-12-04 16:14 ` Christoph Hellwig [this message]
2009-12-07 22:15   ` Nathan Scott
     [not found] <1957734295.979141260224244359.JavaMail.root@mail-au.aconex.com>
2009-12-07 22:17 ` Nathan Scott
     [not found] <404301816.1070071260483145992.JavaMail.root@mail-au.aconex.com>
2009-12-10 22:12 ` Nathan Scott
2009-12-14 22:43   ` Christoph Hellwig

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=20091204161426.GA21499@infradead.org \
    --to=hch@infradead.org \
    --cc=aelder@sgi.com \
    --cc=nathans@debian.org \
    --cc=xfs@oss.sgi.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