From: Tom Rini <trini@kernel•crashing.org>
To: linuxppc-dev@lists•linuxppc.org
Subject: Re: Incoming to hostme.bitkeeper.com:/ua/repos/p/ppc/linuxppc_2_4
Date: Thu, 28 Nov 2002 20:01:35 -0700 [thread overview]
Message-ID: <20021129030135.GD25660@opus.bloom.county> (raw)
In-Reply-To: <200211290248.SAA27913@hostme.bitkeeper.com>
On Thu, Nov 28, 2002 at 06:48:10PM -0800, ppc@bkbits•net wrote:
> ChangeSet@1•722, 2002-11-28 19:44:54-07:00, trini@kernel•crashing.org
> Merge kernel.crashing.org:/home/trini/work/kernel/pristine/linux_2_4
> into kernel.crashing.org:/home/trini/work/kernel/pristine/linuxppc_2_4
> TAG: v2.4.20_linuxppc_2_4
>
> Makefile@1•178, 02-11-28 19:44:13-07:00, trini@kernel•crashing.org
> Auto merged
>
> ChangeSet@1•2.2.167, 2002-11-28 19:43:57-07:00, trini@kernel•crashing.org
> patch-2.4.20-rc4-final
> TAG: v2.4.20
>
> Makefile@1•19.1.157, 02-11-28 08:55:34-07:00, trini@kernel•crashing.org
> Import patch patch-2.4.20-rc4-final
And with the start of this, all final releases in the linuxppc_2_4 and
linuxppc_2_4_devel trees will have a tag for the merge of that release
into that tree. Which means that in a linuxppc_2_4_devel tree, bk
export -tplain -rv2.4.20_linuxppc_2_4_devel will get the
linuxppc_2_4_devel tree, as of 2.4.20.
Tags might be added to previous revisions if time permits, or someone
produces a nifty script to find out what revisions corrispond to what :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2002-11-29 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200211290248.SAA27913@hostme.bitkeeper.com>
2002-11-29 3:01 ` Tom Rini [this message]
[not found] <20010816172318.F1E97FE57@hostme.bitkeeper.com>
2001-08-16 17:32 ` Incoming to hostme.bitkeeper.com:/ua/repos/p/ppc/linuxppc_2_4 Tom Rini
2001-08-17 5:46 ` Paul Mackerras
2001-08-17 14:47 ` Tom Rini
2001-08-17 19:28 ` 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=20021129030135.GD25660@opus.bloom.county \
--to=trini@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)linuxppc.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