Re: drivers/net/usb/hso.c on sparc32

[Denis Joseph Barrow <D.Barow@xxxxxxxxxx>]

Hi Alan,
I use quilt for posting all my patches,
I can get around this quite well,
never tried stgit though.

Us guys at option are using linux-usb to post & watch bugs the hso driver
we want to stick with this mailing list I see no reason to change.
However I now realise I'm being naive/stupid/sloppy but I pull my hso driver which I
apply patches to at the moment from linus'es official tree.
I take it Greg KH is the linux-usb official maintainer how do I pull
his tree. I'll watch the serious bugs & fix these
but as best I can but I'd like somebody else to take care of the warnings
on sparc etc. & fix them under my nose.

I'd better suscribe to the linux-usb mailing list,
If you guys can handle thousands
I suppose I can handle 10 or so additional emails a day.

Alan Cox wrote:
>> is fast enough to be a really good maintainer I just about
>> manage to get a linux release candidate about every 10-12 days.
>> I want to be a primary contributor to hso.c but the internal version I maintain
>> is not whats in the official tree also as much as I love git I'm a bit of a clown with it, I
>> keep making mistakes with it, I've succeeding in corrupting clearcase 
>> repositorys in the past but clearcase is rubbish compared to git, I love git.
> 
> You might find tools like quilt/stgit are actually more useful for
> maintaining patches on top of a git tree. I certainly do as they are much
> more flexible.
> 
>>> It's been a usb thing, so linux-usb is good.
> 
> Can we agree which tree hso is going via. I've got stuff in ttydev for it
> which at the moment does depend on the ttydev tree queue but after that
> it would be nice to have a definitive correct tree - which I think is
> linux-usb in this case ?
> 
> Alan


-- 
best regards,
D.J. Barrow
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html