From: Rob Landley <rob@landley.net>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org, dwmw2@infradead.org,
linux-next@vger.kernel.org, linux-m68k@lists.linux-m68k.org
Subject: Re: make headers_install broken for ARCH=m68k in 2.6.29-rc7.
Date: Tue, 17 Mar 2009 23:03:58 -0500 [thread overview]
Message-ID: <200903172304.00157.rob@landley.net> (raw)
In-Reply-To: <49BEDC75.1080704@snapgear.com>
On Monday 16 March 2009 18:10:45 Greg Ungerer wrote:
> >> git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
> >> fix-includes
...
> Did you get the "fix-includes" branch?
Quite possibly not. (I'm not a git person.)
I did a "git clone git://blah fix-includes" of the branch you gave a URL to,
checked for tags and saw nothing particularly interesting, did a log -v and
exported an archive of the most recent commit, and built it.
(Just tried it again with the same result.)
What _should_ I have done?
Rob
next prev parent reply other threads:[~2009-03-18 4:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903120437.03837.rob@landley.net>
[not found] ` <20090312095854.GA9398@uranus.ravnborg.org>
2009-03-12 20:03 ` make headers_install broken for ARCH=m68k in 2.6.29-rc7 Rob Landley
2009-03-12 20:58 ` Sam Ravnborg
2009-03-12 23:24 ` Stephen Rothwell
2009-03-12 21:02 ` Sam Ravnborg
2009-03-12 22:40 ` Geert Uytterhoeven
2009-03-13 3:25 ` Rob Landley
2009-03-13 7:04 ` Greg Ungerer
2009-03-13 8:25 ` Sam Ravnborg
2009-03-13 8:33 ` Geert Uytterhoeven
2009-03-13 8:59 ` Sam Ravnborg
2009-03-13 10:52 ` Greg Ungerer
2009-03-13 12:14 ` Geert Uytterhoeven
2009-03-16 12:40 ` Greg Ungerer
2009-03-16 20:20 ` Rob Landley
2009-03-16 22:08 ` Geert Uytterhoeven
2009-03-16 23:09 ` Greg Ungerer
2009-03-16 23:10 ` Greg Ungerer
2009-03-18 4:03 ` Rob Landley [this message]
2009-03-18 5:34 ` Greg Ungerer
2009-03-18 18:12 ` Rob Landley
2009-03-18 23:53 ` Greg Ungerer
2009-03-19 7:59 ` Geert Uytterhoeven
2009-03-19 8:41 ` Rob Landley
2009-03-13 8:25 ` Geert Uytterhoeven
2009-03-13 6:53 ` Greg Ungerer
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=200903172304.00157.rob@landley.net \
--to=rob@landley.net \
--cc=dwmw2@infradead.org \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-next@vger.kernel.org \
--cc=sam@ravnborg.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).