From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: -tip: origin tree build failure (was: [GIT PULL] ext4 update for 2.6.37)
Date: Thu, 28 Oct 2010 18:38:54 +0200 [thread overview]
Message-ID: <20101028163854.GA15450@elte.hu> (raw)
In-Reply-To: <AANLkTi=8SbOZizWpxLg=Bgp7atdgr8MsR6tnRDYr1+eW@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Thu, Oct 28, 2010 at 12:56 AM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > Today's -tip fails to build due to upstream commit 5dabfc7 ("ext4: rename
> > {exit,init}_ext4_*() to ext4_{exit,init}_*()"), on all[yes/mod]config with
> > CONFIG_EXT4_FS_XATTR disabled:
>
> Btw, could you try to write these things so that the changelog doesn't have to be
> totally rewritten? Now I always end up having to move things around and edit them
> to be useful from a long-term perspective, which is kind of silly.
Heh, i was just lazy and used sfr's linux-next build bug reporting mails as a
template ;-)
Point taken in any case, i'll read your edited changelog and will change the
template accordingly.
Would this:
Upstream commit 5dabfc7 ("ext4: rename {exit,init}_ext4_*() to
ext4_{exit,init}_*()"), breaks the build on all[yes/mod]config with
CONFIG_EXT4_FS_XATTR disabled:
...
have been better?
Thanks,
Ingo
next prev parent reply other threads:[~2010-10-28 16:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 4:52 [GIT PULL] ext4 update for 2.6.37 Theodore Ts'o
2010-10-28 4:52 ` Theodore Ts'o
2010-10-28 7:50 ` Markus Trippelsdorf
2010-10-28 7:56 ` -tip: origin tree build failure (was: [GIT PULL] ext4 update for 2.6.37) Ingo Molnar
2010-10-28 7:56 ` Ingo Molnar
2010-10-28 12:12 ` Theodore Tso
2010-10-28 12:12 ` Theodore Tso
2010-10-28 16:30 ` Linus Torvalds
2010-10-28 16:38 ` Ingo Molnar [this message]
2010-10-28 16:55 ` Ted Ts'o
2010-10-28 17:00 ` Linus Torvalds
2010-10-28 17:17 ` Ingo Molnar
2010-10-28 17:17 ` Ingo Molnar
2010-10-28 17:27 ` Minimum git commit abbrev length (Was Re: -tip: origin tree build failure (was: [GIT PULL] ext4 update) " Ted Ts'o
2010-10-28 18:28 ` Linus Torvalds
2010-10-28 18:54 ` Linus Torvalds
2010-10-29 0:14 ` Minimum git commit abbrev length (Was Re: -tip: origin tree build failure Brandon Casey
2010-10-28 21:39 ` Junio C Hamano
2010-10-28 21:50 ` Linus Torvalds
2010-10-28 21:50 ` Linus Torvalds
2011-03-10 22:37 ` [PATCH] find_unique_abbrev(): honor caller-supplied "len" better Junio C Hamano
2011-03-10 23:07 ` Linus Torvalds
2011-03-11 0:40 ` Junio C Hamano
2011-03-11 1:16 ` Linus Torvalds
2011-03-11 1:33 ` Junio C Hamano
2011-03-11 2:21 ` Linus Torvalds
2011-03-11 3:09 ` Junio C Hamano
2011-03-11 3:03 ` Junio C Hamano
2011-03-11 5:22 ` Jeff King
2011-03-11 5:33 ` Jeff King
2011-03-11 22:45 ` Junio C Hamano
2011-03-13 13:30 ` Namhyung Kim
2011-03-19 1:22 ` Jay Soffian
2011-03-19 16:24 ` Namhyung Kim
2010-11-01 16:34 ` ext3 patches related to uninitialized memory references Roman Borisov
-- strict thread matches above, loose matches on Subject: below --
2010-10-28 14:39 -tip: origin tree build failure (was: [GIT PULL] ext4 update for 2.6.37) Ingo Molnar
2010-10-28 14:39 ` Ingo Molnar
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=20101028163854.GA15450@elte.hu \
--to=mingo@elte.hu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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.