From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Wolfgang Grandegger <wg@domain.hid>
Cc: adeos-main <adeos-main@gna.org>, Wolfgang Denk <wd@domain.hid>
Subject: Re: [Adeos-main] Re: [RFC] git workflow
Date: Wed, 20 Dec 2006 14:13:25 +0100 [thread overview]
Message-ID: <458936F5.2090006@domain.hid> (raw)
In-Reply-To: <458925AA.6000404@domain.hid>
Wolfgang Grandegger wrote:
> A while ago I also played a bit with stgit and I was also not convinced,
> that it's the right tool for our purpose. Nevertheless, I could reduce
> the amount of git trees to manage (but I have to spend more time for a
> better judgment).
>
> Currently I'm porting IPIPE v1.6 over arch/powerpc rising a few code
> management issues. I started porting with i386-1.6-01 extracting the
> common part from that patch and adapting the arch specify code for
> arch/powerpc. Now IPIPE is at v1.6-02 and I realized various
> modifications, also of the noarch part including some serious bug fixes
> (local_irq_disable_head in main.c did hang my system). But now, there is
> no easy way to update the noarch part as we deal with combined noarch +
> arch patches. From a new git based code management system, I would
> appreciate a separation of noarch and arch. This would make it easier to
> keep the archs in sync with Philippe's reference implementation (for
> x86). Any comments?
IMHO, having the noarch and arch code separated is a nuisance. If there
was a centralized ipipe branch for 2.6.19, you would simply synchronize
your working copy with the server using the equivalent of "cvs/svn
update" and "cvs/svn commit". On the other hand, if the arch and noarch
code was separated, you would end up with twice as much updates and
commits.
--
Gilles Chanteperdrix
next prev parent reply other threads:[~2006-12-20 13:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 18:16 [Adeos-main] [RFC] git workflow Jan Kiszka
2006-12-19 13:31 ` [Adeos-main] " Jan Kiszka
2006-12-19 13:45 ` Gilles Chanteperdrix
2006-12-19 13:57 ` Jan Kiszka
2006-12-19 14:23 ` Gilles Chanteperdrix
2006-12-19 14:40 ` Jan Kiszka
2006-12-19 16:42 ` Wolfgang Denk
2006-12-19 16:59 ` Jan Kiszka
2006-12-19 21:30 ` Wolfgang Denk
2006-12-20 9:33 ` Jan Kiszka
2006-12-20 11:59 ` Wolfgang Grandegger
2006-12-20 13:13 ` Gilles Chanteperdrix [this message]
2006-12-20 13:38 ` Wolfgang Grandegger
2006-12-20 13:49 ` Jan Kiszka
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=458936F5.2090006@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=adeos-main@gna.org \
--cc=wd@domain.hid \
--cc=wg@domain.hid \
/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.