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

> Have you ever tried what you're talking about or is it a guess ?

I just did that.  I have Linus's tree and tags, and Ralf's tree:

git checkout mips
git diff v2.6.14..HEAD

the nice thing about git is that it was written to do exactly the sort 
of things we need it to do, like this.

> 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 ?

Linus wrote a HOWTO on that very subject:

http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt

> 2 - The way branches are made is broken : you can not fetch separate
> branches without doing some "grafts" things

I'm no git expert, but can't you just

git-pull rsync://ftp.linux-mips.org/git/linux.git remote:local

That works for me.

Regards,
Jordan

-- 
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>

  parent reply	other threads:[~2006-01-10 17:27 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
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 [this message]
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=20060110173813.GA25480@cosmic.amd.com \
    --to=jordan.crouse@amd.com \
    --cc=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