From: Rob Landley <rob@landley.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>, Rich Felker <dalias@libc.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
musl@lists.openwall.com, libc-alpha@sourceware.org,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [musl] Re: SH sigcontext ABI is broken
Date: Sat, 20 Jun 2015 14:59:38 -0500 [thread overview]
Message-ID: <5585C62A.5060301@landley.net> (raw)
In-Reply-To: <CAMuHMdWqBh4xJiiEO6a6QQzTrjUJ99w4Bxf3ZkBBBNVk6FNkhA@mail.gmail.com>
On 06/20/2015 03:10 AM, Geert Uytterhoeven wrote:
> On Fri, Jun 19, 2015 at 10:32 PM, Rich Felker <dalias@libc.org> wrote:
>> On Fri, Jun 19, 2015 at 09:57:22PM +0200, Andreas Schwab wrote:
>>> Rich Felker <dalias@libc.org> writes:
>>>
>>>> Thanks, but most of the links seem to be broken.
>>>
>>> Are they? I'm only seeing a single broken link, which has a mirror.
>>
>> My bad. Indeed only the davej one is broken, but that's where the code
>> must have been introduced (even the earliest commit in tglx
>> history.git has the #ifdef __SH4__ for FPU regs) and I can't find a
>> cgit interface to it. Fetching several GB to browse history locally is
>> going to take a while if I have to do that..
>
> Using web interfaces for archeology doesn't fly.
> If you're doing serious Linux work, you should already have a git repository
> of the kernel. full-history-linux.git.tar weights in at only ca. 0.5 giB.
I have a somewhat updated version of that at
http://landley.net/kdocs/local/linux-fullhist.tar.bz2 which I should
probably update for the 4.0 release. (It's pulled to 3.0 currently.)
Meanwhile you can download and extract that tarball, cd into it, then
"git checkout -f" followed by "git pull". (It doesn't have the checked
out files because it would make the tarball bigger, it's just the .git
directory.) That gives you a repository that goes from 0.0.1 to current,
although I haven't gone back and tagged the old releases yet.
Oh, you may want to edit .git/config so it pulls from linux instead of
linux-2.6. Largely cosmetic, but eh...
> Gr{oetje,eeting}s,
>
> Geert
Rob
--
To unsubscribe from this list: send the line "unsubscribe linux-sh" in
next prev parent reply other threads:[~2015-06-20 19:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 7:09 Rich Felker
2015-06-19 7:41 ` Andreas Schwab
2015-06-19 19:12 ` Rich Felker
2015-06-19 19:57 ` [musl] " Andreas Schwab
2015-06-19 20:32 ` Rich Felker
2015-06-20 8:10 ` [musl] " Geert Uytterhoeven
2015-06-20 19:59 ` Rob Landley [this message]
2015-07-02 19:23 ` Maciej W. Rozycki
2015-07-02 22:51 ` Rob Landley
2015-07-03 6:43 ` Andreas Schwab
2015-06-20 18:06 ` Rich Felker
2015-06-24 4:25 ` [musl] " Rob Landley
2015-06-24 4:52 ` Rich Felker
2015-06-24 7:12 ` [musl] " Rob Landley
2015-06-24 18:03 ` Rich Felker
2015-06-24 8:40 ` [musl] " Rob Landley
2015-06-24 21:34 ` Rich Felker
2015-06-24 22:32 ` Rob Landley
2015-06-24 23:26 ` Bobby Bingham
2015-06-24 23:54 ` Rich Felker
2015-06-25 6:24 ` [musl] " Geert Uytterhoeven
2015-06-24 14:10 ` Joseph Myers
2015-06-24 8:23 ` Rob Landley
2015-06-24 18:12 ` Rich Felker
2015-06-24 9:14 ` Rob Landley
2015-06-24 22:02 ` Rich Felker
2015-06-24 19:37 ` Joseph Myers
2015-06-24 20:08 ` Rich Felker
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=5585C62A.5060301@landley.net \
--to=rob@landley.net \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-sh@vger.kernel.org \
--cc=musl@lists.openwall.com \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).