Re: [iPAQ] HH Patches

Tim,

On Sunday 03 February 2002 22:06, Tim Riker wrote:
>I know many, in fact probably most, of the patches have been submitted.

<sigh> That is not what you stated earlier.

You are now attempting to change the subject from HH.org does not cooperate
with the rest of the community to CVS verses patches. I am not going to play
games with you. If you have a problem that you want to help fix, great. If
not, please do not waste my time.

I have not implied, that all kernel folk work with CVS trees. HH.org has
chosen to use CVS for various reasons, that is where the "complete" patches
for HH.org reside! Please note that I clearly referred you to RMK's
automated patch system, not CVS.

If somebody wants patches, it is trivial to create a HH patch from the CVS
tree. For complete instructions on how to use CVS, I recommend that you get
"Open Source Development with CVS" by Fogel a CoriolisOpen Press publication
or see http://www.cvshome.org/docs/manual/cvs.html

The merging of patches from HH.org has been timely and frequent. Please see
the URL's that I gave you in my previous e-mail. The current system of
merging patches into the mainstream takes a long time, so we maintain a
separate tree. "This is the current system that has been in place for
getting new patches into the Linux kernel. It has been this way for a very
long time. If you do not like the way the system works, I would suggest that
you take it up with RMK and Linus."

RMK and others have public patch systems. We use these systems. I
see no reason to duplicate their efforts.

--George

On Sunday 03 February 2002 22:06, Tim Riker wrote:
> Not upset, just ranting.
>
> I know many, in fact probably most, of the patches have been submitted.
> But yet the community at large replies with the response that cvs is the
> sole source. This mentality is what should be fixed. It leads to dual
> development paths and does not foster good interproject communication.
>
> The community at large should be made more aware of the repository
> listed below.
>
> Standard releases like familiar should have patches available for the
> open source packages they include.
>
> These patches should be mailed promptly to the package maintainers.
>
> CVS is a useful tool. However a commit is not, and should not be the end
> of the road.
>
> There are many things in handhelds CVS that are pushed upstream.
> Excellent work with these!
>
> I did not mean to offend. I was just ranting. Perhaps I've spoken more
> clearly now?
>
> Now a nitpick:
> > "This is the current
> > system that has been in place for getting new patches into the Linux
> > kernel. It has been this way for a very long time. If you do not like
> > the way the system works, I would suggest that you take it up with RMK
> > and Linus."
>
> You imply that all the kernel folk work as per HH with CVS trees that
> they all share. "This" is not the case. The patches are the way things
> work. I do not have issues with that. It has worked well for me as well
> with projects I maintain. I think Linus has expressed similar concerns
> with the growing list of kernel cvs servers.
>
> The CVS trees around the net have forked off on many occasions and died
> out. I'm just pointing out that HH is not working as well with the
> community in this respect as it could. This is NOT to say that there is
> no cooperation. Many things have come from HH and been merged into the
> mainstream. I would expect that you would agree with me when I say these
> merges could be more timely and more frequent. I would suggest that
> better, more public, patch maintenance would help.
>
> How many members of the HH community have a good feel for where HH
> differs from mainstream linux (in this case rmk)? I would say few. They
> just pull whatever is current from cvs. Patches make these differences
> more obvious. It also makes those who use the patches more vocal as to
> their needs such that the mainstream better fits those needs.
>
> George France wrote:
> > Tim,
> >
> > Calm down.
> >
> > Please see:
> >
> > http://www.arm.linux.org.uk/developer/patches/
> >
> > more specificly:
> >
> > http://www.arm.linux.org.uk/developer/patches/?action=section&section=0
> > http://www.arm.linux.org.uk/developer/patches/?action=section&section=20
> >
> > You will see that, every patch is sent up stream. Sometimes to the ARM
> > maintainer Russell King (RMK). Sometimes to the maintainer. Most of the
> > time, these patches are accepted, sometimes they are not. Even if a
> > patch is accepted, the user will have to wait until the next kernel.org
> > Linux release or RMK patch release until the new code is available.
> >
> > Andrew is 100% correct. The "complete" hh.org patches are only
> > available through the linux/kernel CVS tree on handhelds.org. This is
> > the current system that has been in place for getting new patches into
> > the Linux kernel. It has been this way for a very long time. If you do
> > not like the way the system works, I would suggest that you take it up
> > with RMK and Linus. I would welcome any improvements.
> >
> > Best Regards,
> >
> > --George
> >
> > On Sunday 03 February 2002 15:09, Tim Riker wrote:
> > > <rant>
> > >
> > > Which, of course, means they have never been sent to the upstream
> > > maintainers in a legible format.
> > >
> > > See previous email thread on why upstream maintainers will not grep
> > > around everyone's cvs tree looking for useful bits.
> > >
> > > </rant>
> > >
> > > "Christian, Andrew" wrote:
> > > > The hh patches are only available through the linux/kernel CVS
> > > > repository.
> > > >
> > > > - Andrew
> > > >
> > > > > -----Original Message-----
> > > > > From: Klaus Reimer [mailto:k@ailis.de]
> > > > > Sent: Saturday, February 02, 2002 6:09 AM
> > > > > To: ipaq@handhelds.org
> > > > > Subject: [iPAQ] HH Patches
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > is there a location where the hh-Kernel-Patches can be
> > > > > downloaded separately?
> > > > > Or are they only available together with the kernel sources in the
> > > > > linux/kernel CVS repository?
> > > > >
> > > > > --
> > > > > Bye, K
> > > > > [A735 47EC D87B 1F15 C1E9 53D3 AA03 6173 A723 E391]
> > > > > (Finger k@ailis.de to get public key)
> > > > > _______________________________________________
> > > > > iPAQ mailing list
> > > > > iPAQ@handhelds.org
> > > > > http://handhelds.org/mailman/listinfo/ipaq
> > > > > irc://irc.openprojects.net #ipaq
> > > >
> > > > _______________________________________________
> > > > iPAQ mailing list
> > > > iPAQ@handhelds.org
> > > > http://handhelds.org/mailman/listinfo/ipaq
> > > > irc://irc.openprojects.net #ipaq
Received on Sun Feb 3 22:16:23 2002