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,
Paul Mackerras <paulus@samba•org>
Subject: Re: linuxppc trees, what is going on ?
Date: Mon, 19 Jan 2004 17:38:57 +0100 [thread overview]
Message-ID: <20040119163857.GB23613@iliana> (raw)
In-Reply-To: <20040119155801.GF13454@stop.crashing.org>
On Mon, Jan 19, 2004 at 08:58:01AM -0700, Tom Rini wrote:
> 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.
Yeah, but i am not sure i fully understand. In this case, bk changes in
linuxppc-2.4 yields :
ChangeSet@1•1058.1.312, 2004-01-04 19:34:56-02:00, marcelo@logos•cnet
Import 2.4.24 final tree
ChangeSet@1•1058.1.311, 2004-01-04 19:32:02-02:00, marcelo@logos•cnet
Cset exclude: laforge@netfilter•org|ChangeSet|20031204183256|31723
ChangeSet@1•1058.1.310, 2004-01-04 19:31:23-02:00, marcelo@logos•cnet
Cset exclude: jt@bougret•hpl.hp.com|ChangeSet|20031213132008|01226
ChangeSet@1•1058.1.309, 2004-01-04 19:31:05-02:00, marcelo@logos•cnet
Cset exclude: trini@mvista•com|ChangeSet|20031210203050|36304
ChangeSet@1•1058.1.308, 2004-01-04 19:28:46-02:00, marcelo@logos•cnet
Cset exclude: bjorn.helgaas@hp•com|ChangeSet|20031218183339|13120
ChangeSet@1•1058.235.6, 2004-01-04 17:53:50-02:00, marcelo@logos•cnet
Change EXTRAVERSION to 2.4.24-rc1
TAG: v2.4.24
TAG: v2.4.24-rc1
None of them seem related to when the linux-2.4 changeset got merged
into linuxppc-2.4.
Friendly,
Sven Luther
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-19 16:38 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
2004-01-19 16:38 ` Sven Luther [this message]
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=20040119163857.GB23613@iliana \
--to=sven.luther@wanadoo$(echo .)fr \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=paulus@samba$(echo .)org \
--cc=trini@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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