From: xfs@oss.sgi.com
To: xfs@oss.sgi.com
Subject: [XFS updates] XFS development tree branch, for-next, updated. xfs-for-linus-3.17-rc3-33-g2f43bbd
Date: Sun, 28 Sep 2014 19:03:13 -0500 (CDT) [thread overview]
Message-ID: <20140929000314.2D6447F92@oss.sgi.com> (raw)
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
2f43bbd Merge branch 'xfs-trans-recover-cleanup' into for-next
b818cca xfs: refactor recovery transaction start handling
7656066 xfs: reorganise transaction recovery item code
88b863d xfs: fix double free in xlog_recover_commit_trans
e9131e5 xfs: recovery of XLOG_UNMOUNT_TRANS leaks memory
eeb1168 xfs: refactor xlog_recover_process_data()
from 33044dc408e6e6bb7f270c0a2e12598ef5592987 (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.
- Log -----------------------------------------------------------------
commit 2f43bbd96e43d0b85803f5092be94bbb92d8eac9
Merge: 33044dc b818cca
Author: Dave Chinner <david@fromorbit.com>
Date: Mon Sep 29 10:00:24 2014 +1000
Merge branch 'xfs-trans-recover-cleanup' into for-next
-----------------------------------------------------------------------
Summary of changes:
fs/xfs/xfs_log_recover.c | 564 ++++++++++++++++++++++++++---------------------
1 file changed, 308 insertions(+), 256 deletions(-)
hooks/post-receive
--
XFS development tree
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2014-09-29 0:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140929000314.2D6447F92@oss.sgi.com \
--to=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.