From: Simon Richter <Simon.Richter@hogyros.de>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: merge progress
Date: Tue, 11 Oct 2005 14:31:23 +0200 [thread overview]
Message-ID: <434BB09B.9070605@hogyros.de> (raw)
In-Reply-To: <17227.44943.714106.911471@cargo.ozlabs.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
Hi,
Paul Mackerras wrote:
> I have just pushed out a new pile of commits to the powerpc-merge tree
> on kernel.org. (It may take a little while for them to get mirrored
> from master.kernel.org to ftp/rsync.kernel.org.)
Should I fast-forward the APUS patches towards the merge tree, or is it
better to apply them in the unmerged tree and merge them back into the
merge tree from there?
Simon
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 307 bytes --]
next prev parent reply other threads:[~2005-10-11 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 12:26 merge progress Paul Mackerras
2005-10-11 12:31 ` Simon Richter [this message]
2005-10-17 11:01 ` Paul Mackerras
2005-10-17 22:19 ` Simon Richter
2005-10-18 7:50 ` Geert Uytterhoeven
2005-10-17 22:39 ` Kumar Gala
2005-10-11 18:54 ` Arnd Bergmann
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=434BB09B.9070605@hogyros.de \
--to=simon.richter@hogyros.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.