From: Charles Wilson <cwilson@ece.gatech.edu>
To: Jason Tishler <jason@tishler.net>
Cc: Jörg <Joerg.Schaible@gft.com>, cygwin-list <cygwin@sources.redhat.com>
Subject: Re: CVS Problems: Updated: gdbm-1.8.0-4
Date: Fri, 01 Mar 2002 07:50:00 -0000 [thread overview]
Message-ID: <3C7FA2AB.5060208@ece.gatech.edu> (raw)
In-Reply-To: <20020301131228.GC2604@hp.com>
Jason Tishler wrote:
> Chuck,
>
> On Thu, Feb 28, 2002 at 12:18:35PM -0500, Charles Wilson wrote:
>
>>Well, the current cygwin port of CVS seems to store all 'normal' files
>>in the repository in LF/CR mode. On checkout (from a local repository)
>>all 'normal' files are created in LF/CR mode. This is *regardless* of
>>whether the local working directory is on a binmount or textmount. (Of
>>course, the repository is on a binmount; see (a) above).
>>
>
> Is the above really true? I have empirical evidence to the contrary.
> I just tried a local repository cvs init, import, and checkout with all
> mounts in bin mode. All files in the repository and working directories
> end up in LF mode.
?????
I had precisely the OPPOSITE experience -- with all mounts in bin mode.
I started with files with LF endings. I imported them -- and the new
repository files had LF/CR. I then checked them out (to a separate
location) -- and the new working dir had LF/CR.
Damn. I'm gonna have to look at this harder...
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-03-01 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 2:19 "Schaible, Jörg"
2002-02-28 9:19 ` Charles Wilson
2002-02-28 9:31 ` Charles Wilson
2002-03-01 7:08 ` Jason Tishler
2002-03-01 7:50 ` Charles Wilson [this message]
2002-03-01 1:55 Peter Ring
2002-03-04 0:43 "Schaible, Jörg"
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=3C7FA2AB.5060208@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=Joerg.Schaible@gft.com \
--cc=cygwin@sources.redhat.com \
--cc=jason@tishler.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).