Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ivan Korzakow <ivan.korzakow@gmail.com>
To: "P. Christeas" <p_christ@hol.gr>
Cc: linux-mips@linux-mips.org
Subject: Re: why the early_initcall(au1x00_setup) do not work?
Date: Tue, 10 Jan 2006 17:38:55 +0100	[thread overview]
Message-ID: <a59861030601100838oa89ac84n@mail.gmail.com> (raw)
In-Reply-To: <200601101757.45297.p_christ@hol.gr>

2006/1/10, P. Christeas <p_christ@hol.gr>:
> On Tuesday 10 January 2006 5:40 pm, Ivan Korzakow wrote:
> > 2006/1/10, Ralf Baechle <ralf@linux-mips.org>:
> > > On Tue, Jan 10, 2006 at 09:02:43AM +0800, zhuzhenhua wrote:
> > > > > In 2.6.15 things were alomst fully merged but several megabytes of
> > > > > patches are between the linux-mips.org and kernel.org versions of
> > > > > 2.6.14.
> > > > >
> > > > >   Ralf
> > > >
> > > > in linux-mips, where to download the patches for standard kernel?
> > >
> > > I don't publish such patches - but they're eassy to generate.
> >
> > Could you be a bit more explicit about that "easy" way you generate them ?
> >
> > Ivan
> You make sure you have the two trees and diff them.
> They 're both in git and typically you could do that only using git.
>

Have you ever tried what you're talking about or is it a guess ?
For example, let's say that there's a bug introduced when merging
Linus tree with mips branch. How do you easily "bisect" in order to do
a binary seek of this bug ?

BTW, I noticed that Linux mips repository have several branches. Each
branch is tracking each kernel minor version. I think this is
completly useless :
1 - it makes the repository huge by keeping history since 2.2 (It's
pointless for most people)
2 - The way branches are made is broken : you can not fetch separate
branches without doing some "grafts" things

Why not simply ask Linus to pull from the mips tree ?

Ivan

  reply	other threads:[~2006-01-10 16:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09  5:59 why the early_initcall(au1x00_setup) do not work? zhuzhenhua
2006-01-09 14:56 ` Ralf Baechle
2006-01-09 15:20   ` P. Christeas
2006-01-09 15:24     ` Ralf Baechle
2006-01-10  1:02       ` zhuzhenhua
2006-01-10 14:19         ` Ralf Baechle
2006-01-10 15:40           ` Ivan Korzakow
2006-01-10 15:57             ` P. Christeas
2006-01-10 16:38               ` Ivan Korzakow [this message]
2006-01-10 16:57                 ` P. Christeas
2006-01-10 17:15                   ` Ivan Korzakow
2006-01-10 23:20                     ` Ralf Baechle
2006-01-11 15:17                       ` Ivan Korzakow
2006-01-10 21:53                   ` Ralf Baechle
2006-01-11 11:10                     ` Ivan Korzakow
2006-01-11 11:20                       ` Ralf Baechle
2006-01-11 15:07                         ` Ivan Korzakow
2006-01-11 19:07                           ` Ralf Baechle
2006-01-11 15:14                     ` Ivan Korzakow
2006-01-10 17:38                 ` Jordan Crouse
2006-01-11  2:04           ` zhuzhenhua
2006-01-11 12:16             ` Ralf Baechle

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=a59861030601100838oa89ac84n@mail.gmail.com \
    --to=ivan.korzakow@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=p_christ@hol.gr \
    /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