From: Philippe Gerum <rpm@xenomai.org>
To: "Steven A. Falco" <sfalco@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] SVN versus git
Date: Wed, 20 Aug 2008 19:14:28 +0200 [thread overview]
Message-ID: <48AC50F4.8090109@domain.hid> (raw)
In-Reply-To: <48AB34DC.4080907@domain.hid>
Steven A. Falco wrote:
> I just downloaded the current SVN Xenomai trunk, and in
> ksrc/arch/powerpc/patches/README, it says that patch
> 2.6.26-DENX-2.2-04/powerpc is based on git commit
> 5abf5fb22279f8b409203a160365edbd51b16406
>
> However, if I try to find that commit in the ipipe-2.6
> tree (from the DENX site), the commit is not found.
>
git://www.denx.de/git/linux-2.6-denx.git
> What is the relationship between the SVN and git
> repositories?
The I-pipe code is maintained in the ipipe-2.6 GIT tree, patches are made from
that tree, and published there http://download.gna.org/adeos/patches/. Some of
those patches (well, most of them actually) are picked by the Xenomai project
and committed to the SVN repo.
Should I be able to find that commit,
> or is it in a private tree?
>
The reference tree is DENX's one.
> One other comment: I don't even see a branch called
> ipipe-2.6.26-powerpc in the git tree, but I do see
> arm, x86, and noarch there. Am I looking at the wrong
> tree?
No, I'm just late pushing this branch out of my local tree. I need to rebase it
on DENX-v2.6.26-stable first.
>
> Steve
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>
--
Philippe.
prev parent reply other threads:[~2008-08-20 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 21:02 [Xenomai-help] SVN versus git Steven A. Falco
2008-08-20 17:14 ` 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=48AC50F4.8090109@domain.hid \
--to=rpm@xenomai.org \
--cc=sfalco@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.