On Tue, Jun 03, 2014 at 10:38:16AM +0100, WorMzy Tykashi wrote: > I noticed this in another thread: > > On 3 June 2014 10:14, David Sterba <dste...@suse.cz> wrote: > > I've assembled a branch containing doc-only fixes, including this one, > > and asked Chris do do a 3.14.3 release. > > Does this branch include this fix for this bug? According to > patchwork, it's status is still "under review", but it's been a month > and the bug slipped into the 3.14.2 release. I just want to make sure > it hasn't fallen out of the pile. :)
Yes the branch contains this fix as well, http://repo.or.cz/w/btrfs-progs-unstable/devel.git/shortlog/refs/heads/v3.14.x and it almost fell off, I had forgotten to tag it in my mailbox and a filter did not pick it. About patchwork, I'm still using mailbox and git for tracking patches and sync the patchwork status manually on occasion. This is not ideal and patchwork status is not accurate. I'm aiming for a semi-automated sync from git/mbox -> patchwork when the patches change their status regarding stability and upstream readiness. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
