linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: linuxppc-dev@ozlabs.org
Subject: Master and powerpc-next branches reset
Date: Tue, 10 Jun 2008 21:45:12 +1000	[thread overview]
Message-ID: <18510.26952.733823.290697@cargo.ozlabs.ibm.com> (raw)

Due to the "Free a PTE bit on ppc64 with 64K pages" commit from Ben H
turning out to be bad, I have reset the master and powerpc-next
branches of the powerpc.git repository to the commit just before that,
and then reapplied the "powerpc: Remove arch/ppc and include/asm-ppc"
commit (taking the opportunity to add John Linn's acked-by).

So if you pull either or both of those branches, you'll need to do a
git pull -f next time.  I prefer not to reset branches if possible,
but it seemed necessary to remove the bad commit in this case so as
not to cause bisection problems later.

Paul.

                 reply	other threads:[~2008-06-10 11:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=18510.26952.733823.290697@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=linuxppc-dev@ozlabs.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).