From owner-freebsd-fs@freebsd.org  Mon Jan 11 20:14:51 2016
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57CDBA6BD71
 for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 11 Jan 2016 20:14:51 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 483321D82
 for <freebsd-fs@FreeBSD.org>; Mon, 11 Jan 2016 20:14:51 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0BKEof7014913
 for <freebsd-fs@FreeBSD.org>; Mon, 11 Jan 2016 20:14:51 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 205816] [ext2fs] [patch] EXT4 sparse blocks unsupported,
 contain garbage when read
Date: Mon, 11 Jan 2016 20:14:51 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: koobs@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: pfg@FreeBSD.org
X-Bugzilla-Flags: mfc-stable9? mfc-stable10?
X-Bugzilla-Changed-Fields: flagtypes.name
Message-ID: <bug-205816-3630-g8QQzUHUAI@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205816-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-205816-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2016 20:14:51 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205816

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|mfc-stable10+               |mfc-stable10?

--- Comment #14 from Kubilay Kocak <koobs@FreeBSD.org> ---
@Pedro The mfc-stableX flags are used to track when/after a change has been
committed to the respective branch (+, meaning done), or in the case where =
it
wont, or shouldn't be (-, with comment). If you're not sure, leave the valu=
e as
?=20

You can mouse-over the flag names for more detail and example usage/meaning

--=20
You are receiving this mail because:
You are on the CC list for the bug.=