All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: Re: [XFS updates] XFS development tree branch, for-next, updated. xfs-for-linus-v3.14-rc1-2-12935-ga64b760
Date: Fri, 14 Feb 2014 09:45:37 +1100	[thread overview]
Message-ID: <20140213224537.GL13997@dastard> (raw)
In-Reply-To: <20140213223525.B7E517F57@oss.sgi.com>

On Thu, Feb 13, 2014 at 04:35:24PM -0600, xfs@oss.sgi.com wrote:
> This is an automated email from the git hooks/post-receive script. It was
> generated because a ref change was pushed to the repository containing
> the project "XFS development tree".
> 
> The branch, for-next has been updated
>   discards  39f30ca7eaa4fe9224094c7a9964cff36c584dab (commit)
>   discards  008482657169c0276ddd2ba00a1ad14a324b91f0 (commit)
>   a64b760 Merge branch 'xfs-async-aio-extend' into for-next
>   692f68a Merge branch 'xfs-fixes-for-3.15-1' into for-next
>   55daffa xfs: xfs_sb_read_verify() doesn't flag bad crcs on primary sb
>       from  39f30ca7eaa4fe9224094c7a9964cff36c584dab (commit)
> 
> Those revisions listed above that are new to this repository have
> not appeared on any other notification email; so we list those
> revisions in full, below.

Just a note for everyone because this is the first time it has
happened since this discussion:

http://oss.sgi.com/archives/xfs/2013-12/msg00586.html

This update is a rebase of the for-next branch as the initial topic
branch that forms the current base of the for-next tree
(xfs-fixes-for-3.14-rc3) was updated. The commit 55daffa mentioned
above is the new commit that was added to that that branch.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

      reply	other threads:[~2014-02-13 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 22:35 [XFS updates] XFS development tree branch, for-next, updated. xfs-for-linus-v3.14-rc1-2-12935-ga64b760 xfs
2014-02-13 22:45 ` Dave Chinner [this message]

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=20140213224537.GL13997@dastard \
    --to=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.