From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Purser <purserj@ksit.dynalias.com>
Cc: git@vger.kernel.org
Subject: Re: Cogito Tutorial If It Helps
Date: Thu, 28 Apr 2005 10:51:05 +1000 [thread overview]
Message-ID: <1114649466.7183.210.camel@gaston> (raw)
In-Reply-To: <1114649337.7112.208.camel@gaston>
On Thu, 2005-04-28 at 10:48 +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2005-04-27 at 06:52 +1000, James Purser wrote:
> > I reworked the previous tutorial to take in the changes in the scripts.
> > Will make this a series of tutorials to cover all aspects. Any
> > suggestions or hints or spelling corrections would be most welcome.
> >
> > http://ksit.dynalias.com/articles.php?s_id=46&art_id=41
>
> Hrm... this tutorial is exactly like cogito's own readme as far as I'm
> concerned : it just makes things even more confusing to me. I must be
> really stupid, I should stick to hacking the kernel and not try to use
> userland tools :)
>
> Anyway, can you explain what it is all about this branch thing ?
>
> I don't understand why in hell you would want linux-2.6 to be a branch
> of cogito itself ...
Forget it, I must be lacking caffeine this morning, you are adding linus
git, not linux-2.6 as a branch which makes a lot more sense... sorry
for the noise.
Ben.
next prev parent reply other threads:[~2005-04-28 0:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 20:52 Cogito Tutorial If It Helps James Purser
2005-04-26 21:18 ` Petr Baudis
2005-04-26 21:36 ` James Purser
2005-04-26 21:40 ` Petr Baudis
2005-04-27 18:22 ` Alan Chandler
2005-04-27 19:32 ` Petr Baudis
2005-04-27 22:15 ` Alan Chandler
2005-04-28 5:40 ` Alan Chandler
2005-04-28 0:48 ` Benjamin Herrenschmidt
2005-04-28 0:51 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 0:45 James Purser
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=1114649466.7183.210.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=git@vger.kernel.org \
--cc=purserj@ksit.dynalias.com \
/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.