linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Sven Luther <sven.luther@wanadoo.fr>, linuxppc-dev@lists.linuxppc.org
Subject: Re: linuxppc trees, what is going on ?
Date: Tue, 13 Jan 2004 18:18:27 +0100	[thread overview]
Message-ID: <20040113171827.GA13841@iliana> (raw)
In-Reply-To: <20040113170631.GD10912@stop.crashing.org>


On Tue, Jan 13, 2004 at 10:06:31AM -0700, Tom Rini wrote:
> On Mon, Jan 12, 2004 at 08:32:17AM +0100, Sven Luther wrote:
>
> > Ok, anyway linuxppc_2_4 is supposed to be dead. But my point was, from
> > which TAG should i extract kernels from the linuxppc-2.4 to make debian
> > packages ? I tried the v2.4.24 tag, which seemed ok, but the version was
> > still 2.4.24-rc1. I guess this was a problem due to the haste of the
> > 2.4.24 release or something, but it would be nice if it was clear which
> > tag we should export.
>
> There is no tag you can use to do this.  Just like how 'v2.4.24' in the
> old linuxppc_2_4* trees would get you 2.4.24 w/o any PPC changes, the
> same will happen here.

This is getting more complicated ...

Ok, let's say, tomorrow i need to release a debian 2.4.24 powerpc
package, what should i take for this, and which tag/date/whatever should
i use.

Upto now, i was using the linuxppc_2_4 tree, and the corresponding
linuxppc tag. I had the impression from Paul's mail that i should now
take the linuxppc-2.4 tree and the v2.4.24 tag, but from what you tell,
this will include less stuff than what i previously did.

Also, there is the fact that modern powermac will most probably need
stuff from the -benh tree, and that it would be maybe nicer for me to
follow that tree instead.

Ok, back to RTC code now, still wondering how the OF parsing stuff
works, not convinced about reading prom.c and prom.h.

Friendly,

Sven Luther

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-01-13 17:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10  8:41 linuxppc trees, what is going on ? Sven Luther
2004-01-12  1:21 ` Paul Mackerras
2004-01-12  7:32   ` Sven Luther
2004-01-13 17:06     ` Tom Rini
2004-01-13 17:18       ` Sven Luther [this message]
2004-01-13 17:35         ` Tom Rini
2004-01-14  8:55           ` Sven Luther
2004-01-18 12:21           ` Sven Luther
2004-01-19 15:29             ` Tom Rini
2004-01-19 15:47               ` Sven Luther
2004-01-19 15:58                 ` Tom Rini
2004-01-19 16:38                   ` Sven Luther
2004-01-19 16:48                     ` Tom Rini
2004-01-19 17:07                       ` Sven Luther
2004-01-19 17:22                         ` Tom Rini
2004-01-19 17:30                           ` Sven Luther
2004-01-19 17:42                             ` Geert Uytterhoeven
2004-01-19 17:48                               ` Tom Rini
2004-01-19 17:49                               ` Sven Luther
2004-01-19 17:53                                 ` Geert Uytterhoeven
2004-03-15 10:31                                   ` linuxppc latest ? Armin Schindler
2004-03-16  6:38                                     ` Kumar Gala
2004-01-19 17:43                             ` linuxppc trees, what is going on ? Tom Rini
     [not found]                               ` <20040123154058.GA15605@work.bitmover.com>
2004-01-23 15:49                                 ` Tom Rini
2004-01-13 17:04   ` 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=20040113171827.GA13841@iliana \
    --to=sven.luther@wanadoo.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).