All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfs: for-next branch updated to cddc116
Date: Fri, 29 May 2015 08:05:49 -0400	[thread overview]
Message-ID: <20150529120549.GA36053@bfoster.bfoster> (raw)
In-Reply-To: <20150528222109.GC4316@dastard>

On Fri, May 29, 2015 at 08:21:09AM +1000, Dave Chinner wrote:
> On Fri, May 29, 2015 at 07:53:09AM +1000, Dave Chinner wrote:
> > Hi folks,
> > 
> > The for-next branch of the xfs kernel repository at
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git
> > 
> > has just been updated.
> > 
> > The new head of the for-next branch is commit:
> > 
> > cddc116 xfs: xfs_iozero can return positive errno
> 
> Note: i just updated it again with a patch I missed in the
> xfs-for-linus-v4.1-rc6 branch:
> 
> Brian Foster (1):
>       [22419ac] xfs: fix broken i_nlink accounting for whiteout tmpfile inode
> 

Any word on the following two as well?

http://oss.sgi.com/pipermail/xfs/2015-April/041504.html
http://oss.sgi.com/pipermail/xfs/2015-May/041582.html

Brian

> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com



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

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

  reply	other threads:[~2015-05-29 12:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 21:53 [ANNOUNCE] xfs: for-next branch updated to cddc116 Dave Chinner
2015-05-28 22:21 ` Dave Chinner
2015-05-29 12:05   ` Brian Foster [this message]
2015-05-29 22:31     ` Dave Chinner
2015-05-30 12:06       ` Brian Foster

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=20150529120549.GA36053@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=david@fromorbit.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 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.