Issues retaining a DOS' file encoding when committing it into a UNIX repository
|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
 |
Issues retaining a DOS' file encoding when committing it into a UNIX repository
by hectorub
::
Rate this Message:
Hi,
I'm having trouble committing DOS text files into a UNIX repository. By 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 ------------------------------------ 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/ |
|
|
Re: Issues retaining a DOS' file encoding when committing it into a UNIX repository
by syntevo Support-4
::
Rate this Message:
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 correct line separators locally using a script. -- Best regards, Thomas Singer _____________ syntevo GmbH http://www.syntevo.com "hectorub" <hurdaneta@...> wrote: > Hi, > > I'm having trouble committing DOS text files into a UNIX repository. By 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 ------------------------------------ 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/ |
|
|
|
|
|
Re: Issues retaining a DOS' file encoding when committing it into a UNIX repository
by syntevo Support-4
::
Rate this Message:
> Or, um, commit them in binary mode?
That is possible, but IMHO the worst choice, because then you will have no merging any more (and the repository might grow much faster). -- Best regards, Thomas Singer _____________ syntevo GmbH http://www.syntevo.com Mike Ralphson <mike.ralphson@...> wrote: > 2009/3/23 syntevo Support <smartcvs@...>: > >> When I commit DOS files > >> into the repository I see that the ,v files gets saved in 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? > > > > 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 > > correct line separators locally using a script. > > Or, um, commit them in binary mode? > > Mike ------------------------------------ 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/ |
|
|
|
|
|
Re: Issues retaining a DOS' file encoding when committing it into a UNIX reposi
by hectorub
::
Rate this Message:
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@..., 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 > correct line separators locally using a script. > > -- > Best regards, > Thomas Singer > _____________ > syntevo GmbH > http://www.syntevo.com > > > "hectorub" <hurdaneta@...> wrote: > > > Hi, > > > > I'm having trouble committing DOS text files into a UNIX repository. By 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 > ------------------------------------ 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/ |
|
|
RE: Re: Issues retaining a DOS' file encoding when committing it into a UNIX reposi
by Greg Gibeling
::
Rate this Message:
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 > correct line separators locally using a script. > > -- > Best regards, > Thomas Singer > _____________ > syntevo GmbH > http://www.syntevo.com > > > "hectorub" <hurdaneta@...> wrote: > > > Hi, > > > > I'm having trouble committing DOS text files into a UNIX repository. By > > 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/ |
|
|
Re: Re: Issues retaining a DOS' file encoding when committing it into a UNIX reposi
by syntevo Support-4
::
Rate this Message:
Hi Hector,
> When you say set the correct line separators using a > script, could you give me some more detail. Well, are you sure you need different line separators in the working copy? Or do you need them only in the "output of the working copy", e.g. packages for different operating systems? If the latter case, then changing the line separators in the build script (e.g. ANT) would be the best solution. > 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. Copying in SVN costs nearly nothing. It is quite similar to hard links in the Unix world. -- Best regards, Thomas Singer _____________ syntevo GmbH http://www.syntevo.com "hectorub" <hurdaneta@...> wrote: > 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@..., 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 > > correct line separators locally using a script. > > > > -- > > Best regards, > > Thomas Singer > > _____________ > > syntevo GmbH > > http://www.syntevo.com > > > > > > "hectorub" <hurdaneta@...> wrote: > > > > > Hi, > > > > > > I'm having trouble committing DOS text files into a UNIX repository. By 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 > > > > > > > ------------------------------------ > > Yahoo! Groups Links > > > > ------------------------------------ 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/ |
|
|
Re: Issues retaining a DOS' file encoding when committing it into a UNIX reposi
by hectorub
::
Rate this Message:
Thank you Thomas for your replies. Also, thank you Greg for your notes on SmartSVN. I'll take another stab at SVN.
Hector --- In smartcvs@..., syntevo Support <smartcvs@...> wrote: > > Hi Hector, > > > When you say set the correct line separators using a > > script, could you give me some more detail. > > Well, are you sure you need different line separators in the working copy? Or > do you need them only in the "output of the working copy", e.g. packages for > different operating systems? If the latter case, then changing the line > separators in the build script (e.g. ANT) would be the best solution. > > > 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. > > Copying in SVN costs nearly nothing. It is quite similar to hard links in the > Unix world. > > -- > Best regards, > Thomas Singer > _____________ > syntevo GmbH > http://www.syntevo.com > > > "hectorub" <hurdaneta@...> wrote: > > > 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@..., 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 > > > correct line separators locally using a script. > > > > > > -- > > > Best regards, > > > Thomas Singer > > > _____________ > > > syntevo GmbH > > > http://www.syntevo.com > > > > > > > > > "hectorub" <hurdaneta@> wrote: > > > > > > > Hi, > > > > > > > > I'm having trouble committing DOS text files into a UNIX repository. By 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 > > > > > > > > > > > > > ------------------------------------ > > > > Yahoo! Groups Links > > > > > > > > > ------------------------------------ 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/ |
| Free embeddable forum powered by Nabble | Forum Help |
