From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Please review trini/canadian-sdk branch
Date: Thu, 1 Jan 2009 22:32:35 +0100 [thread overview]
Message-ID: <c384c5ea0901011332w109a42euec5bfcefb3100ca5@mail.gmail.com> (raw)
In-Reply-To: <20081222211049.GB4287@smtp.west.cox.net>
Hello Tom,
On Mon, Dec 22, 2008 at 10:10 PM, Tom Rini <trini@kernel.crashing.org> wrote:
> Hey all. Can people please review the trini/canadian-sdk branch, in
> terms of content? If things are good at this point content-wise, I'll
> split the commits up roughly along the lines of the original patches in
> http://bugs.openembedded.net/show_bug.cgi?id=4664 but with checksums
> added in each new commit.
>
I noticed your *poke* but I'm new on inspecting branches with GIT.
How could I easily browse through the content? I think I would like to
see the changed and newly added content in an easy way.
Also, do you have any pointers on how to use the canadian sdk stuff?
Maybe a tested build I might reproduce?
Regards,
--
Leon
next prev parent reply other threads:[~2009-01-01 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 21:10 Please review trini/canadian-sdk branch Tom Rini
2009-01-01 21:32 ` Leon Woestenberg [this message]
2009-01-01 21:56 ` Tom Rini
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=c384c5ea0901011332w109a42euec5bfcefb3100ca5@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.