linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: linux-sh@vger.kernel.org
Subject: Re: [musl] Re: SH sigcontext ABI is broken
Date: Thu, 02 Jul 2015 19:23:49 +0000	[thread overview]
Message-ID: <alpine.LFD.2.11.1507022016190.31747@eddie.linux-mips.org> (raw)
In-Reply-To: <20150619070912.GA15025@brightrain.aerifal.cx>

On Sat, 20 Jun 2015, Rob Landley wrote:

> >>>> 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.)

 For the record the LMO tree <git://git.linux-mips.org/pub/scm/ralf/linux> 
has a full history recorded and is in sync with kernel.org.  There's some 
GIT magic that cuts some operations like `git log' at 2.6.12-rc2, but you 
can go beyond that if you know the right commit id, e.g.:

$ git log -p 66f0a432 -- arch/sh

I can see the initial SH import was with 2.3.19.

  Maciej

  parent reply	other threads:[~2015-07-02 19:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  7:09 SH sigcontext ABI is broken Rich Felker
2015-06-19  7:41 ` Andreas Schwab
2015-06-19 19:12 ` [musl] " Rich Felker
2015-06-19 19:57 ` Andreas Schwab
2015-06-19 20:32 ` Rich Felker
2015-06-20  8:10 ` Geert Uytterhoeven
2015-06-20 18:06 ` [musl] " Rich Felker
2015-06-20 19:59 ` [musl] " Rob Landley
2015-06-24  4:25 ` [musl] " Rob Landley
2015-06-24  4:52 ` Rich Felker
2015-06-24  7:12 ` Rob Landley
2015-06-24  8:23 ` Rob Landley
2015-06-24  8:40 ` Rob Landley
2015-06-24  9:14 ` Rob Landley
2015-06-24 14:10 ` Joseph Myers
2015-06-24 18:03 ` Rich Felker
2015-06-24 18:12 ` Rich Felker
2015-06-24 19:37 ` Joseph Myers
2015-06-24 20:08 ` Rich Felker
2015-06-24 21:34 ` Rich Felker
2015-06-24 22:02 ` Rich Felker
2015-06-25  6:24 ` Geert Uytterhoeven
2015-07-02 19:23 ` Maciej W. Rozycki [this message]
2015-07-02 22:51 ` [musl] " Rob Landley
2015-07-03  6:43 ` Andreas Schwab

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=alpine.LFD.2.11.1507022016190.31747@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=linux-sh@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).