linuxppc-dev.lists.ozlabs.org archive mirror
 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: Mon, 19 Jan 2004 08:58:01 -0700	[thread overview]
Message-ID: <20040119155801.GF13454@stop.crashing.org> (raw)
In-Reply-To: <20040119154758.GA23038@iliana>


On Mon, Jan 19, 2004 at 04:47:58PM +0100, Sven Luther wrote:

> On Mon, Jan 19, 2004 at 08:29:54AM -0700, Tom Rini wrote:
> > > I did pull the linux-2.4 tree, and exported the v2.4.24 tag. I did the
> > > same for the linuxppc-2.4 tree, and diffed the two exported trees. Both
> > > were exactly the same.
> >
> > That is correct. A tag has the same values (set of ChangeSets)
> > regardless of the tree (simpilication).
>
> Ok, how are you then supposed to make a diff of the powerpc relative
> changes ? You use the changeset just above the merge or something ?

The process I described about (that you snipped) is how you find the
ChangeSet of when 'linux-2.4' at a certain point is merged into
'linuxppc-2.4', and that ChangeSet will point to something like 2.4.24 +
powerpc changes.

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

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

  reply	other threads:[~2004-01-19 15:58 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
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 [this message]
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=20040119155801.GF13454@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 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).