All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Korzakow <ivan.korzakow@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "P. Christeas" <p_christ@hol.gr>, linux-mips@linux-mips.org
Subject: Re: why the early_initcall(au1x00_setup) do not work?
Date: Wed, 11 Jan 2006 16:07:25 +0100	[thread overview]
Message-ID: <a59861030601110707u16f5d366m@mail.gmail.com> (raw)
In-Reply-To: <20060111112001.GA4403@linux-mips.org>

2006/1/11, Ralf Baechle <ralf@linux-mips.org>:
> On Wed, Jan 11, 2006 at 12:10:05PM +0100, Ivan Korzakow wrote:
>
> > It would be great to be a little bit more explicit by giving some
> > _little_ examples ! Why not enlighting us directly instead of being so
> > vague.
>
> In books that kind of stuff is usually marked as "left as an exercise to
> the reader" ;-)

yeah, but we are chating on a forum ;0)

>
>   git-clone rsync://ftp.linux-mips.org/pub/scm/linux.git repository
>   cd repository
>   git-fetch git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 master:linus
>   git-repack -a -d
>

I know that but you miss my point. GIT is a tool to ease work on linux
kernel, but the way you use it makes harder life of users of your
tree. For example your tree contains more than 350 000 objects ! That
makes a lot of git commands running slow...

Let's say I'm developing a net drivers on ARM platform. I'm actually
do not care about ARM development, but I do care about net tree. To do
that, I just need to clone net tree because I know that ARM should be
OK with this tree. What about MIPS ?

I'm just wondering why not asking to Linus to pull from your tree like
every others maintainers do ?

Ivan

  reply	other threads:[~2006-01-11 15:04 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 [this message]
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=a59861030601110707u16f5d366m@mail.gmail.com \
    --to=ivan.korzakow@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=p_christ@hol.gr \
    --cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.