From: Philippe Gerum <rpm@xenomai.org>
To: Richard Cochran <richardcochran@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Virtual IRQ Numbers in powerpc?
Date: Mon, 02 Nov 2009 21:00:19 +0100 [thread overview]
Message-ID: <1257192019.2210.5.camel@domain.hid> (raw)
In-Reply-To: <20091102095437.GA19825@domain.hid>
On Mon, 2009-11-02 at 10:54 +0100, Richard Cochran wrote:
> On Sun, Oct 25, 2009 at 12:13:45AM +0200, Philippe Gerum wrote:
> >
> > adeos-ipipe-2.6.30-powerpc-DENX-2.7-00: fine
> > adeos-ipipe-2.6.30.3-powerpc-DENX-2.7-01: BROKEN
> > adeos-ipipe-2.6.30.3-powerpc-DENX-2.7-02: fine
>
> I am using git to track ipipe, but these two commits
>
> da0e45d1e84389bdf5e750e9179767fd274f7031
> 9010961a407699a3908d7c2a842a8ece6084cee3
>
> don't show up when I pull from
>
> git://git.denx.de/ipipe-2.6.git
>
> I think that is because the commit are not in any branch. I think they
> should be in branch ipipe-2.6.30-powerpc.
>
> See this:
>
> http://git.denx.de/?p=ipipe-2.6.git;a=shortlog;h=9010961a407699a3908d7c2a842a8ece6084cee3
Those commits seem to still be in flight from my remote staging tree to
the public one, waiting for a mirroring to happen. They are indeed part
of ipipe-2.6.30-powerpc; those are actually the latest commits on top of
2.7-01, leading to 2.7-02.
>
> Richard
>
>
>
--
Philippe.
prev parent reply other threads:[~2009-11-02 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 17:05 [Xenomai-help] Virtual IRQ Numbers in powerpc? A. Nolson
2009-10-24 17:37 ` Philippe Gerum
2009-10-24 18:42 ` A. Nolson
2009-10-24 22:07 ` Philippe Gerum
2009-10-26 15:18 ` [Xenomai-help] Supported Architecture? Matthias Frauendorf
2009-10-26 19:43 ` Pierre Ficheux
2009-10-24 22:13 ` [Xenomai-help] Virtual IRQ Numbers in powerpc? Philippe Gerum
2009-11-02 9:54 ` Richard Cochran
2009-11-02 20:00 ` Philippe Gerum [this message]
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=1257192019.2210.5.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=richardcochran@domain.hid \
--cc=xenomai@xenomai.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.