public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: Nathan Scott <nathans@aconex.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Anibal@oss.sgi.com, Monsalve Salazar <anibal@debian.org>,
	xfs <xfs@oss.sgi.com>
Subject: Re: [PATCH 2/2] xfsprogs: update deb package maintainer, bump version
Date: Wed, 10 Nov 2010 17:32:10 -0600	[thread overview]
Message-ID: <1289431930.1925.14.camel@doink> (raw)
In-Reply-To: <477680717.25681289427570428.JavaMail.root@acxmail-au2.aconex.com>

On Thu, 2010-11-11 at 09:19 +1100, Nathan Scott wrote:
> Hi Alex,
> 
> ----- "Alex Elder" <aelder@sgi.com> wrote:
> 
> > On Wed, 2010-11-10 at 10:53 +1100, Nathan Scott wrote:
> > > No worries - do you have an ETA there Alex?
> > 
> > I wanted to update them and re-post and get
> > an actual review this time.
> > 
> > I can get that done with a few hours effort.
> > What is your time frame?  I'm in the middle of a
> > few things right now but can move this to the
> > front of my queue if you're short on time.
> 
> Ideally we'd get a release out asap for Debian folks,
> as the upgrade issue is biting quite a few people.  If
> the metadump stuff needs more time, doing a subsequent
> release with that is a fine option too... lemme know.
> Since Debian is moving toward a (distro) release, the
> less change we're putting into this release, the better
> - so, my vote would be to hold off on further changes
> till next time, but up to you.

Fine with me.  The metadump stuff doesn't need much time
but I don't mind marking a release without it.  Push your
changes to the xfsprogs-dev tree and I'll put together
the release first thing tomorrow.

I'm not sure where you sent these patches the first time
but I seem to have missed them.  In the future please
send this sort of thing to the list for review.

					-Alex

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

  reply	other threads:[~2010-11-10 23:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <318337928.18811289303806950.JavaMail.root@acxmail-au2.aconex.com>
2010-11-09 11:57 ` [PATCH 2/2] xfsprogs: update deb package maintainer, bump version nathans
2010-11-09 13:39   ` Christoph Hellwig
2010-11-09 23:53     ` Nathan Scott
2010-11-10 17:36       ` Alex Elder
2010-11-10 22:19         ` Nathan Scott
2010-11-10 23:32           ` Alex Elder [this message]
2010-11-11  3:42             ` Nathan Scott
2010-11-11 16:03               ` Alex Elder
2010-11-11 16:05                 ` Christoph Hellwig
2010-11-11 22:06                 ` Nathan Scott
     [not found] <1594229862.31491289470719849.JavaMail.root@acxmail-au2.aconex.com>
2010-11-11 10:24 ` nathans
2010-11-11 16:24   ` Alex Elder
2010-11-11 22:02     ` Nathan Scott

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=1289431930.1925.14.camel@doink \
    --to=aelder@sgi.com \
    --cc=Anibal@oss.sgi.com \
    --cc=anibal@debian.org \
    --cc=hch@infradead.org \
    --cc=nathans@aconex.com \
    --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