linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Costabel <Martin.Costabel@univ-rennes1.fr>
To: laures@esiea.fr
Cc: linuxppc-user@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: Releasing more easy kernel patches
Date: Tue, 25 May 1999 18:27:48 +0100	[thread overview]
Message-ID: <374ADD94.BE39D764@univ-rennes1.fr> (raw)
In-Reply-To: 199905221002.FAA22379@lists.linuxppc.org


laures@esiea.fr wrote:
> 
> Hi,
> 
> I like to try patches on my various kernels. Unfortunately for the mid
> power users like me, it's not always possible to get the bleeding edge
> source tree for cvs, and anyway patches does not seem to be
> always released against this tree.
> 
> As Linuxppc-pre-R5 "ships" with a kernel source that has usb and pcmcia
> stuff (so it's fairly complete), I think it would be reasonable to use
> this tree (which is easy to get and install as well) as a reference for
> all patches released for public testing here (I'm not talking of
> linuxppc-dev).

I think this is a good idea, but why not take the reference release as a
reference? I think right now this is the same thing (rpms version
2.2.6-15a in ftp://ftp.linuxppc.org/linuxppc-dev-rel/1.0/RedHat/RPMS/ or
one of its mirrors), but I have the impression that pre-R5 may change
anytime without notice, whereas RR-1.0 should be a bit more stable
(until, of course, LinuxPPC-R5 hits the net :-)).

> I feel this need because the new sound/brightness patch for PowerBook
> didn't apply without any fuss into this kernel, mac-on-linux gives tons
> of redefinition warnings (although the kernel works fairly well), there
> were minor problems with latest Geert's aty patch etc etc.
> I would be really more confident if the patches were released
> specifically for my version of the kernel.
> 
> If hard kernel hackers don't find the time to do that by themselves,
> it's ok to send me the patch and I'll try to get the "correct" patch as
> soon as posible. (be prepared to questions then...)
[patch deleted]

--
Martin
P.S. Did you really send your message on last Saturday? It arrived only
today in my mailbox.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

      reply	other threads:[~1999-05-25 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-22 11:35 Releasing more easy kernel patches laures
1999-05-25 17:27 ` Martin Costabel [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=374ADD94.BE39D764@univ-rennes1.fr \
    --to=martin.costabel@univ-rennes1.fr \
    --cc=costabel@wanadoo.fr \
    --cc=laures@esiea.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-user@lists.linuxppc.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).