RE: Re: Issues retaining a DOS' file encoding when committing it into a UNIX reposi

                I once thought as you do now, but while the tag is logically
a copy, it doesn't actually make a copy of the data.  My understanding is
that SVN tags, like all CVS and SVN revisions, use a delta-compression
scheme to only store the changes between two versions of a file (or a file
and a tagged version of it).

That said, as a longtime and very heavy duty user of SVN now, I haven't
needed a tag since I started using it.  Because an SVN revision number
applies to every file in the repository (unlike CVS revisions which are
per-file), a tag is really just a textual name for a revision, and in fact
we usually just use revision numbers now, since they're so much more
convenient and require no extra effort to create.

 

-Greg

 

From: smartcvs@... [mailto:smartcvs@...] On Behalf
Of hectorub
Sent: Monday, March 23, 2009 9:09 AM
To: smartcvs@...
Subject: [smartcvs] Re: Issues retaining a DOS' file encoding when
committing it into a UNIX reposi

 

Hi Thomas,

Thanks for the reply. When you say set the correct line separators using a
script, could you give me some more detail.

I've looked at SVN && SmartSVN but was disappointed with the way tags are
handled. A copy of the repository every time it gets tagged is too costly.
Or is my understanding incorrect?

Thanks
Hector Urdaneta

--- In smartcvs@... <mailto:smartcvs%40yahoogroups.com> ,
syntevo Support <smartcvs@...> wrote:
>
> Hi Hector,
>
> > When I commit DOS files
> > into the repository I see that the ,v files gets saved in UNIX format.
>
> You should not worry about how file content is stored in the ,v files,
because
> this is CVS server internal. SmartCVS always converts the line separators
to
> the correct line separator for the repository (\n), just like any other
> correctly working CVS client.
>
> > So in short, what do I need to do to ensure that DOS text files get
committed
> > into a UNIX repository from a UNIX client in its original DOS format,
and that
> > when I retrieve it on a UNIX OS, its DOS format is preserved?
>
> You only can define what line separator to use for your whole project
> (Project|Settings, Text File Options). You can't define that on a per-file
> base using CVS. If you need that, then you should use (Smart)SVN or set
the UNIX
> > repository I mean one that is stored on a UNIX box. When I commit DOS
files
> > into the repository I see that the ,v files gets saved in UNIX format.
I'm
> > running the smartCVS (professional) client from a Linux machine.
> >
> > My working copy of the repository contains a mix of DOS and UNIX files.
Not
> > knowingly, I originally committed all files into the repository with the
Text
> > File Encoding in the Repository in ASCII mode. I later on changed the
setting
> > to Unicode (UTF-8). Removed the DOS files from the repository and tried
> > committing them once again to the repository. When I look at the ,v file
in
> > the repository I still see that the files are stored in the UNIX format.
> >
> > So in short, what do I need to do to ensure that DOS text files get
committed
> > into a UNIX repository from a UNIX client in its original DOS format,
and that
> > when I retrieve it on a UNIX OS, its DOS format is preserved?
> >
> > Thanks in advance for any help
> > Hector Urdaneta
> > Linear Technology Corporation
>





[Non-text portions of this message have been removed]



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/smartcvs/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/smartcvs/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:smartcvs-digest@...
    mailto:smartcvs-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    smartcvs-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/