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 12:10:05 +0100 [thread overview]
Message-ID: <a59861030601110310gca74f54o@mail.gmail.com> (raw)
In-Reply-To: <20060110215322.GA27577@linux-mips.org>
2006/1/10, Ralf Baechle <ralf@linux-mips.org>:
> On Tue, Jan 10, 2006 at 06:57:24PM +0200, P. Christeas wrote:
>
> > > > 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 ?
> >
> > I was about to mention the git incompatibility as I gave you the first
> > answer. It's true what you say and I also find it annoying. That's why I use
> > Linus tree.
> > I cannot, though, complaint to Ralph about this practice. It seems that he has
> > done his best to preserve the CVS history of his tree. We can only thank him
> > for that. It is just a lot of work to trim the tree and make it
> > Linus-parallel.
> > There is also things that I don't know about git, so I won't jump to
> > conclusions yet (as to whether it is feasible to merge with Linus).
>
> It is possible to keep both Linus's and the lmo tree in the same
> repository with a _little_ care. I do that all the time. When compressed
> this will result in a bloat of just about 10-20MB.
>
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.
Thanks
Ivan
next prev parent reply other threads:[~2006-01-11 11:07 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 [this message]
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=a59861030601110310gca74f54o@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox