Re: bkcvs not up-to-date?

• Next message: Randy.Dunlap: "garbled oopsen"
• Previous message: Ben Collins: "Re: 2.5: ieee1394 still broken, vesafb still broken, ipv6 still broken"
• In reply to: Pavel Machek: "Re: bkcvs not up-to-date?"
• Next in thread: Paul Clements: "Re: bkcvs not up-to-date?"
• Reply: Paul Clements: "Re: bkcvs not up-to-date?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Pavel,

you got Larry's address wrong. It's bitmover.com, not bitmover.org.

Pavel Machek wrote:
>
>>>and checked out the tree, but cvs log Makefile still indicates 2.5.68
>>>is the lastest version. What am I doing wrong?
>>
>>I have the same problem, the CVS gateway got stuck some point in the
>>middle of 2.5.68 and has had no apparen t updates since
>
>
> Its even worse: part of updates gets there. Like CREDITS file is
> up-to-date but Makefile is not.

Carl-Daniel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Randy.Dunlap: "garbled oopsen"
• Previous message: Ben Collins: "Re: 2.5: ieee1394 still broken, vesafb still broken, ipv6 still broken"
• In reply to: Pavel Machek: "Re: bkcvs not up-to-date?"
• Next in thread: Paul Clements: "Re: bkcvs not up-to-date?"
• Reply: Paul Clements: "Re: bkcvs not up-to-date?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed May 07 2003 - 22:00:34 EST