From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev@lists.linuxppc.org
Cc: Paul Mackerras <paulus@samba.org>
Subject: Re: linuxppc-2.4 tree temporarily unavailable
Date: 22 Apr 2003 13:18:13 +0200 [thread overview]
Message-ID: <1051010293.6075.0.camel@gaston> (raw)
In-Reply-To: <1051002731.1091.53.camel@gaston>
On Tue, 2003-04-22 at 11:12, Benjamin Herrenschmidt wrote:
> Hi !
>
> Because of a stupid confusion (we really have too many tree here), I
> broke the linuxppc-2.4 tree on ppc.bkbits.net (this is the tree that
> is clones from marcelo bk 2.4 with the 4xx/8xx updates).
>
> I've temporarily moved that tree to a different name so people don't
> pull the broken changesets, I'm re-cloning a fresh tree and will
> pull back the correct changes to it. Once that's done, the tree will
> be available again, I hope bk will be smart enough to not require
> people with local clones to re-clone.
It should be back now without need to re-clone
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-04-22 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 9:12 linuxppc-2.4 tree temporarily unavailable Benjamin Herrenschmidt
2003-04-22 11:18 ` Benjamin Herrenschmidt [this message]
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=1051010293.6075.0.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).