Re: Problem...

2001-05-06 Thread schmolle

Danijel,

I import a directory containing certain text file to CVS repository. When I do the 
checkout of the same directory, I get a copy of that file with different size than 
before it was imported, and when running diff tool on the two files, I get that the 
files differ totally, with the same text being recognized as different. I guess the 
problem is some text converting,

I'm willing to bet that the file you had problems with somehow is the only one in the 
set (I assume from your statement there were more) that has Windows/DOS style CR/LF 
line endings.

These must have gotten comitted via the import (and not filtered in any way), but when 
you do the checkout / diff, they did get filtered at one stage or another. I have seen 
similar things; files not showing differences in some environments or client/server OS 
combinations and (like in your case) 100% differences in others.

Try to find the original file you imported and open it in vi in a UNIX environment. 
That will clearly show the line endings. (unless you're using Vim in the 
too-smart-for-its-own-good setting; you MAY have to read the odd man page :)

I found that the cleanest way to solve these things (even though that goes against 
some of CVS's record keeping aspects) is to export the file in question, physically 
delete it from the repository (if you don't know how to do that, you had better not 
try it without supervision :), clean it in a UNIX editor and re-add it. Any tags can 
be removed beforehand and re-applied afterwards.

This obviously doesn't work very well for files that have dozens or more revisions 
that you want to hang on to for some reason. In your case, it seems to be just after 
an import, so it could be applicable. (caveat emptor)

Hope this helps,

Schmolle

___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



test

2001-05-06 Thread Tobias Giesen




Tobias Giesen, Composer - ICQ # 97626829
http://www.tobiasgiesen.de

Check out TGTools, my Plug-In Collection
for Finale: http://www.tgtools.de


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: MS Visual C++ Version

2001-05-06 Thread Jerzy Kaczorowski

Hi,

When VC70 comes out there is no problem at all, because it uses totally
different file format as well as a new extension for those new files. The
workspace is now called a solution (*.sln) and a project files are in XML
format with the extension vcproj (*.vcproj).

I am not sure whether VC40 reads a VC60, but I would think so. Anyway, I
have isntalled my VC50 recently just for the very purpose of trying to build
CVS from source and I might send a fixed project file(the missing
annotate.c) if nobody does so faster than me. I think it is a good idea to
keep the files under VC50 format unless somone can provide the VC60 version
that uses some VC60 features which improve the build version (not present in
older versions that is).

I would love, however, to have a zip files of the sources being exported to
Windows machine or I would have to ftp an untared and ungzipped sources from
my Unix box. I think it would really be nice if we have the zip file
available to download from cvshome.org so folks that don't have a Unix box
at hand can eventually try to build the stuff.

Best Regards,
Jerzy


- Original Message -
From: Dennis Jones [EMAIL PROTECTED]
To: Jerzy Kaczorowski [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Saturday, May 05, 2001 3:07 AM
Subject: Re: MS Visual C++ Version


 If VC 5.0 correctly loads 6.0 project files, then I guess I don't really
 have a problem with updating the projects, but what happens when 7.0 comes
 out?  I do not plan to ever upgrade my VC++ beyond 5.0, and there might be
 other persons who are in the same boat (possibly even 4.2 users).  (Does
VC
 4.2 correctly load 6.0 project files?)

 The problem with updating the project files to version 6.0 is that it
opens
 the door to updating them again (to version 7.0, or newer), and the older
 VC++ environments might not be as happy loading 7.0 (or newer) project
files
 as they seem to be loading 6.0 project files.  As soon as the project file
 format changes significantly enough, older environments will stop working.

 - Dennis


 - Original Message -
 From: Jerzy Kaczorowski [EMAIL PROTECTED]
 To: Dennis Jones [EMAIL PROTECTED]; Derek R. Price
 [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
 [EMAIL PROTECTED]
 Sent: Friday, May 04, 2001 11:52 AM
 Subject: Re: MS Visual C++ Version


  Hi,
 
  It will most likely work OK if you feed VC++ 5.0 with the VC60 project,
  workspace or makefiles. VC50 ignores the unknown flags from VC60 all
  together and I believe that VC60 has a greater audience so less people
 will
  struggle with it if the version would be 6.0.
  The project files that are in the CVS sources seem to be for version
5.0.
 
  I would say that a working files for any version are far better than not
  working ones. Either one would do.
  Actually I noticed one more problem for windows source distribution -
the
  sources are having a Unixy line endings. VC++ can handle that for source
  files, but not for project files.
 
  I am also curious as to how could a project file for zlib be missing -
it
  seems to be properly tagged so if the export was done using a release
tag
  then it should be there, no?
 
  Best Regards,
  Jerzy
 
  - Original Message -
  From: Dennis Jones [EMAIL PROTECTED]
  To: Derek R. Price [EMAIL PROTECTED]; [EMAIL PROTECTED];
  [EMAIL PROTECTED]; [EMAIL PROTECTED]
  Sent: Friday, May 04, 2001 8:21 AM
  Subject: Re: MS Visual C++ Version
 
 
   Yes, I use VC++ 5.0.
  
   - Dennis
  
   - Original Message -
   From: Derek R. Price [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
   Sent: Thursday, May 03, 2001 3:14 PM
   Subject: MS Visual C++ Version
  
  
Hey all,
   
Just curious if anybody is still using some version of MSVC++
earlier
than 6.0 to compile CVS on Windows platforms?  In other words, is it
still important to keep the project and make files generated by 4.0,
 as
is currently the case?
   
Derek
   
--
Derek Price  CVS Solutions Architect (
   http://CVSHome.org )
mailto:[EMAIL PROTECTED] CollabNet ( http://collab.net )
--
The policy of the American government is to leave their citizens
free,
   neither
restraining nor aiding them in their pursuits.
   
- Thomas Jefferson
   
   
   
   
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
  
  
   ___
   Info-cvs mailing list
   [EMAIL PROTECTED]
   http://mail.gnu.org/mailman/listinfo/info-cvs
  
 


 ___
 Info-cvs mailing list
 [EMAIL PROTECTED]
 http://mail.gnu.org/mailman/listinfo/info-cvs



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: MS Visual C++ Version

2001-05-06 Thread Laine Stump

Jerzy Kaczorowski [EMAIL PROTECTED] writes:

 When VC70 comes out there is no problem at all, because it uses
 totally different file format as well as a new extension for those
 new files. The workspace is now called a solution (*.sln) and a
 project files are in XML format with the extension vcproj
 (*.vcproj).
 
 I am not sure whether VC40 reads a VC60, but I would think so.

It doesn't. VC4 uses makefiles (.mak), VC5 and VC6 use project and
workspace files (.dsp and .dsw).

 I think it is a good idea to keep the files under VC50 format unless
 somone can provide the VC60 version that uses some VC60 features
 which improve the build version (not present in older versions that
 is).

I think that whoever is donating the time to maintain the make/project
files for VC should do it in whatever format is the most convenient
for them, and everyone else should either live with it, or donate
*their* time to supply project files for the older/newer versions.

___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



RE: cvs with xinetd

2001-05-06 Thread Gianni Mariani



I use MD5 passwords on my RH7.0 system and CVS 1.11 works fine using unix
account authentication in :pserver: mode.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Peter Ajamian
Sent: Saturday, May 05, 2001 7:10 PM
To: Larry Jones; Info-CVS Mailing List
Subject: Re: cvs with xinetd


Peter Ajamian wrote:

 Larry Jones wrote:
 
  I'm having trouble reconciling this information with the
  original report that MD5 passwords don't work, but DES passwords do.

Hrmmm, just thought of another possibility, what version of the crypt
library are the CVS binaries (rpms, etc) built with?  If it's statically
linked and that library does not support the MD5 extensions that would
explain why CVS isn't working with MD5 encrypted passwords.

Regards, Peter

___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: cvs log between tags

2001-05-06 Thread Laine Stump

[EMAIL PROTECTED] (Greg A. Woods) writes:

 [ On Saturday, May 5, 2001 at 19:51:00 (-0400), Larry Jones wrote: ]
  
  cvs -H log says, in part:
  
  -r[revisions]   Specify revision(s)s to list.
 rev1:rev2   Between rev1 and rev2, including rev1 and rev2.
 rev1::rev2  Between rev1 and rev2, excluding rev1 and rev2.
  
  I think :: was new in CVS 1.11.1.
 
 Unfortunately neither are useful for the most common case I want to use
 (which I suspect is what Jim wants too).
 
 I want to find all the log entries between releases, which to me means
 after the first tag and up until and including the second one.  In other
 words I need:
 
   Between rev1 and rev2, excluding rev1 and including rev2.
 
 Seeing that last log entry is just as important as not seeing the first
 one.

Good point. I want (through *some* method) exactly the same
functionality as you, and I imagine many others do too. I had
suggested implementing the :: syntax for log because : was already
there for log and admin, :: was already supported for the admin
command to mean exclusive of the first and last revisions, and my
feeble mind was at the time thinking something along the lines of
since the tag happens *after* the last revision is committed, that
last revision will be included in the logs. Of course that thinking
is flawed... (I hadn't yet noticed, because I was waiting for it to be
in an official release before doing anything with it.)


So is there an actual use for a command that excludes that last
revision from the log? Since this is a newly implemented option, maybe
the meaning can be changed slightly to mean only revisions that were
committed after the first tag, and prior to the last. Since the
revision with the same number as the last tag was, by definition,
committed prior to making the tag, this would give us what we want
(ie, it would include that last revision), and wouldn't skew the
meaning *too much* from what it means elsewhere ;-)

___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



¸ñ·Ï

2001-05-06 Thread hfgh35673


¿©·¯ºÐ¿¡°Ô °¡Àå ÇÊ¿äÇÏ°í À¯ÀÍÇÑ ÄÄÇ»ÅÍ °ü·ÃÇÁ·Î±×·¥À»
ÆÄ°ÝÀûÀ¸·Î ½Ñ °¡°Ý¿¡ °ø±ÞÇÕ´Ï´Ù

ÃֽŰÔÀÓ. À¯Æ¿°ü·ÃÇÁ·Î±×·¥. MP3. ºñµð¿À½Ãµð µîµî
¸ðµç ÇÁ·Î±×·¥À» ÆǸÅÇÕ´Ï´Ù

¹°·Ð ½Å¿ë °ÆÁ¤À» ÀüÇô ½Å°æ¾²Áö ¸¶½Ê½Ã¿ä
¾ÐÃàÈ­ÀϼÓÀÇ ³»¿ëÀ» º¸½ÅÈÄ ÀüÈ­³ª ¸ÞÀÏ·Î ¿¬¶ôÁֽʽÿä
ÀÌ ¸ÞÀÏÀ» º¸³½ ¾ÆÀ̵ð·Î´Â ¿¬¶ôÀÌ µÇÁö ¾Ê½À´Ï´Ù.
¾ÐÃàÈ­Àϼӿ¡ ¿¬¶ôó°¡ ÀÖ½À´Ï´Ù(¸ÞÀÏ.ÀüÈ­¹øÈ£) 

=== Ưº° º¸³Ê½º ½Ãµð¸¦ ÁõÁ¤ÇÕ´Ï´Ù ===

È®½ÇÇÏ°Ô ÈÞ´ëÆùÀ¸·Î ¿¬¶ôÁֽʽÿä
°¨»çÇÕ´Ï´Ù

³¡À¸·Î Çã¶ô¾øÀÌ ¸ÞÀÏÀ» µå¸°°ÍÀ» »ç°úµå¸³´Ï´Ù.±×¸®°í ¿©·¯ºÐÀÇ ¸ÞÀÏÁÖ¼Ò´Â
¹«ÀÛÀ§·Î ¸ð¾ÆÁø°ÍÀÌ´Ï ´Ù¸¥ °ÆÁ¤Àº ÇÏÁö ¾ÊÀ¸¼Åµµ µË´Ï´Ù.  

¹Ø¿¡ À̾îÁö´Â °°Àº±Û¿¡¼­ ¸®½ºÆ®¸¦ ´Ù¿î¹ÞÀ¸½Ç¼ö ÀÖ½À´Ï´Ù.
¸¸ÀÏ ¹Ø¿¡ [ ÀÌ ±ÛÀÌ º¸Àδٸé Á¤»óÀÔ´Ï´Ù ] °¡ º¸ÀÌÁö ¾Ê°Å³ª 
À̾߱â.»õ·Ò µîÀÇ Åë½ÅÇÁ·Î±×·¥À» »ç¿ëÇϽŴٸé 
÷ºÎµÈ È­ÀÏ   CDLIST.HTM  ¸¦ ´Ù¿î¹ÞÀ¸½ÅÈÄ¿¡ °Å±â¼­ ¸®½ºÆ®¸¦ ¹ÞÀ¸½Ã¸é µË´Ï´Ù
   


Title: ÀÌ°÷Àº Á¦¸ñÀÔ´Ï´Ù



ÀÌ ±ÛÀÌ º¸Àδٸé Á¤»óÀÔ´Ï´Ù. ==> ¹Ø¿¡¼­ ¸®½ºÆ® ´Ù¿î¹ÞÀ¸¼¼¿ä.

¿©·¯ºÐ¿¡°Ô °¡Àå ÇÊ¿äÇÏ°í À¯ÀÍÇÑ ÄÄÇ»ÅÍ °ü·ÃÇÁ·Î±×·¥À»
ÆÄ°ÝÀûÀ¸·Î ½Ñ °¡°Ý¿¡ °ø±ÞÇÕ´Ï´Ù

ÃֽŰÔÀÓ. À¯Æ¿°ü·ÃÇÁ·Î±×·¥. MP3. ºñµð¿À½Ãµð µîµî
¸ðµç ÇÁ·Î±×·¥À» ÆǸÅÇÕ´Ï´Ù

¹°·Ð ½Å¿ë °ÆÁ¤À» ÀüÇô ½Å°æ¾²Áö ¸¶½Ê½Ã¿ä
¾ÐÃàÈ­ÀϼÓÀÇ ³»¿ëÀ» º¸½ÅÈÄ ÀüÈ­³ª ¸ÞÀÏ·Î ¿¬¶ôÁֽʽÿä
ÀÌ ¸ÞÀÏÀ» º¸³½ ¾ÆÀ̵ð·Î´Â ¿¬¶ôÀÌ µÇÁö ¾Ê½À´Ï´Ù.
¾ÐÃàÈ­Àϼӿ¡ ¿¬¶ôó°¡ ÀÖ½À´Ï´Ù(¸ÞÀÏ.ÀüÈ­¹øÈ£) 

=== Ưº° º¸³Ê½º ½Ãµð¸¦ ÁõÁ¤ÇÏ°í ÀÖ½À´Ï´Ù ===

È®½ÇÇÏ°Ô ÈÞ´ëÆùÀ¸·Î ¿¬¶ôÁֽʽÿä
°¨»çÇÕ´Ï´Ù

³¡À¸·Î Çã¶ô¾øÀÌ ¸ÞÀÏÀ» µå¸°°ÍÀ» »ç°úµå¸³´Ï´Ù.±×¸®°í ¿©·¯ºÐÀÇ ¸ÞÀÏÁÖ¼Ò´Â
¹«ÀÛÀ§·Î ¸ð¾ÆÁø°ÍÀÌ´Ï ´Ù¸¥ °ÆÁ¤Àº ÇÏÁö ¾ÊÀ¸¼Åµµ µË´Ï´Ù.  

¸®½ºÆ®¸¦ ´Ù¿î¹ÞÀ¸½Ã·Á¸é ¿©±â¸¦ Ŭ¸¯ÇϽÅÈÄ
cdlist.zip ¸¦ ´Ù¿î¹ÞÀ¸½Ã¸é µË´Ï´Ù

¸¸ÀÏ Outlook Express ¸¦ »ç¿ëÇϽô ºÐÁß¿¡ ¸®½ºÆ®°¡ Á¦´ë·Î ´Ù¿îÀÌ µÇÁö ¾Ê´Â´Ù¸é
÷ºÎµÈ È­ÀÏ cdlist.htm À» ¿­°í ´Ù¿î¹ÞÀ¸½Ã¸é µË´Ï´Ù



Question about auto login

2001-05-06 Thread Liwei Chour



Dear Sir:
I use CVS for several month, It is good for me. But I have one question 
about auto-login.

Beacuse Ineed to buildprogram everyday in different machines, I 
should login CVS server, checkout code, 
build code and logout. I want these process automatically, so I write a 
shell command file to do this job. But 
I need login CVS first. How do I write auto-login shell command ?

Sincerely
Liwie Chour in OFFICE



Permissions

2001-05-06 Thread Sudarshan

I have created a project directory by name project2, which has owner by
name sudhi and group projent where in sudhi,anand,arun are the members
of the group. i have created a reposoitory inside that, and have modules
by name projsudhi where in we have several files, now each one of the
group memebers are able to checkout and work  on files, but when they
make changes to some files and commit that back the permissions sets to
their userid and group id, rather than setting as projsudhi as the
group, with this other members are not able to checkout their files
properly.
PLs let me know the solutions for this,

cvs server is on Linux and clients are using wincvs1.2

Thanking all in advance

Sudarshan


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: Question about auto login

2001-05-06 Thread Laine Stump

Liwei Chour [EMAIL PROTECTED] writes:

 I use CVS for several month, It is good for me. But I have one
 question about auto-login.  Beacuse I need to build program everyday
 in different machines, I should login CVS server, checkout code,
 build code and logout. I want these process automatically, so I
 write a shell command file to do this job. But I need login CVS
 first. How do I write auto-login shell command ?

You don't need to. When you first login (successfully) to any cvs
server, the password information is stored in an encrypted form in the
.cvspass file in your home directory. After this initial login, you
never need to use the cvs login command for that same server ever
again. (Yes, .cvspass saves passwords from multiple servers).

(Note: if you want to forget the password for a particular server,
you can run the cvs logout command, which will erase that password
from .cvspass. You will then need to run cvs login again for that
server before you can use it again.)

___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Digest Only Please

2001-05-06 Thread Steve Robertson
 winmail.dat