From: Hubert Kario <kario@wit.edu.pl>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs: integration branch updated
Date: Fri, 1 Jul 2011 09:35:26 +0200 [thread overview]
Message-ID: <201107010935.26784.kario@wit.edu.pl> (raw)
In-Reply-To: <20110630211902.GC4352@carfax.org.uk>
On Thursday 30 of June 2011 23:19:02 Hugo Mills wrote:
> After a reorganisation of patches, and sending a bunch of them to
> Chris, I've also updated the integration branch to match that. It's
> available from:
>=20
> http://git.darksatanic.net/repo/btrfs-progs-unstable.git/
> integration-20110630
>=20
> The shortlog of 17 patches in this branch beyond the ones I've sen=
t
> to Chris is below.
>=20
> Hugo.
Is there a reason why my patch for compilation errors=20
(http://www.spinics.net/lists/linux-btrfs/msg10965.html)
isn't integrated? Without it, I can't compile btrfs-progs with new gcc=20
(4.6.0 20110429):
volumes.c: In function =E2=80=98btrfs_alloc_data_chunk=E2=80=99:
volumes.c:891:6: error: variable =E2=80=98physical=E2=80=99 set but not=
used [-Werror=3Dunused-but-set-variable]
cc1: all warnings being treated as errors
Regards,
Hubert
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-01 7:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 21:19 btrfs-progs: integration branch updated Hugo Mills
2011-06-30 21:25 ` Andreas Philipp
2011-07-01 8:52 ` Hugo Mills
2011-06-30 21:47 ` Andreas Philipp
2011-07-01 8:54 ` Hugo Mills
2011-07-01 1:50 ` Li Zefan
2011-07-01 9:06 ` Hugo Mills
2011-07-01 7:35 ` Hubert Kario [this message]
2011-07-01 19:35 ` Daniel Witzel
2011-07-01 23:03 ` Andreas Philipp
-- strict thread matches above, loose matches on Subject: below --
2011-08-04 22:43 btrfs-progs " Hugo Mills
2011-08-05 20:47 ` Jan Schubert
2011-08-05 20:57 ` Jan Schubert
2011-08-13 13:18 ` Hugo Mills
2011-08-06 12:12 ` Jan Schubert
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=201107010935.26784.kario@wit.edu.pl \
--to=kario@wit.edu.pl \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).