From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: John Levon <levon@movementarian.org>,
kernel list <linux-kernel@vger.kernel.org>,
Larry McVoy <lm@bitmover.com>
Subject: Re: bkcvs not up-to-date?
Date: Thu, 08 May 2003 03:03:29 +0200 [thread overview]
Message-ID: <3EB9ACE1.405@gmx.net> (raw)
In-Reply-To: <20030507231603.GA699@elf.ucw.cz>
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
next prev parent reply other threads:[~2003-05-08 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 11:15 bkcvs not up-to-date? Pavel Machek
2003-05-07 11:57 ` John Levon
2003-05-07 23:16 ` Pavel Machek
2003-05-08 1:03 ` Carl-Daniel Hailfinger [this message]
2003-05-08 2:36 ` Paul Clements
2003-05-10 15:21 ` Larry McVoy
2003-05-10 17:47 ` Pavel Machek
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=3EB9ACE1.405@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=pavel@ucw.cz \
/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