All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: linuxppc-dev@lists.linuxppc.org, Paul Mackerras <paulus@samba.org>
Subject: Re: linuxppc trees, what is going on ?
Date: Tue, 13 Jan 2004 10:35:14 -0700	[thread overview]
Message-ID: <20040113173513.GE10912@stop.crashing.org> (raw)
In-Reply-To: <20040113171827.GA13841@iliana>


On Tue, Jan 13, 2004 at 06:18:27PM +0100, Sven Luther wrote:
> 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.

First, do a bk help changes.  I mention this since I believe the
behavior of -e will change, or has changed.  Then do a 'bk changes' such
that you see all merge changesets.  Then just find that one that
corresponds to when the merge of Marcelo's tree that contained at least
v2.4.24 came in.  If there are changes after v2.4.24, you will have to
back these out from your patch manually (filterdiff or interdiff can probably
help here).

Paul, do you want to start adding tags to the linuxppc-2.4 tree?

> 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.

The same applies here, except it's when linuxppc-2.4 that has v2.4.24 is
merged in.

--
Tom Rini
http://gate.crashing.org/~trini/

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

  reply	other threads:[~2004-01-13 17:35 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
2004-01-13 17:35         ` Tom Rini [this message]
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=20040113173513.GE10912@stop.crashing.org \
    --to=trini@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@samba.org \
    --cc=sven.luther@wanadoo.fr \
    /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.