From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] Differences between 2.x and 3.x, future merging
Date: Sat, 25 Jun 2011 20:21:41 +0200 [thread overview]
Message-ID: <4E062735.4050907@gentoo.org> (raw)
Hello!
The current process of copying changes from 2.x to 3.x or vice versa is
suboptimal, especially with no recent merge commit around.
I would like to start this thread to list and discuss differences
between catalyst 2.x and 3.x so we can then decide what needs to be
merged in which direction and then have a single branch soon (ideally)
or at least two branches with clear and to-the-point diffs.
Difference I have noticed (without searching) so far:
- Subarch "sh4aeb" is not supported on 3.x but 2.x
- Folder ./arch of 2.x is ./modules/catalyst/arch in 3.x
Please add any differences you are aware of. Many thanks!
Best,
Sebastian
next reply other threads:[~2011-06-25 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 18:21 Sebastian Pipping [this message]
2011-06-25 18:26 ` [gentoo-catalyst] Differences between 2.x and 3.x, future merging Matt Turner
2011-06-25 19:20 ` William Hubbs
2011-06-25 20:25 ` William Hubbs
2011-06-25 18:37 ` Raúl Porcel
2011-06-25 18:47 ` Sebastian Pipping
2011-06-26 2:22 ` Matt Turner
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=4E062735.4050907@gentoo.org \
--to=sping@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox