Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
No problem, it was just coincidence that one of the first builds I started testing against the C# code sent back the date. On a side note I think I saw that the server just takes the date sent by the client as a hint but the file will be "marked" with the server's current date. This is not a big deal since I only use the date as a hint to know if the file has been modified so I can use the client's date. Keep up the good work. -- Regards, JuanC "Tony Hoyle" <tmh at nodomain.org> wrote in message news:3e536c62.778955906 at news.cvsnt.org... > On Wed, 19 Feb 2003 09:56:50 +0000, Tony Hoyle <tmh at nodomain.org> > wrote: > > >Software FX Support wrote: > > > >> I am writing my own C# client code so it could be my fault. > >> > >> Every time I commit a file I get a response where the date part is empty, > >> everything else seems normal. An ls command for example will return valid > >> dates. Note that I am not talking about the entries file using the cvs.exe > >> client, I am writing code that is executing the CVS commands and the > >> response I get back from the server does not contain the date (processing > >> the "Checked-in" response) > > I've checked the code and that's the way the original Unix version did > it. There were a couple of versions of cvsnt that sent the timestamp > back (57d seems to have some code to do it) but that's not the > standard. > > Tony >