Re: [fossil-users] Official approved way of moving a repo?
On Tue, 08 Jan, Richard Hipp wrote: > Both windows and unix should look for both filenames. So you > shouldn't ever run into a case where you end up with both (unless > some of your machines are running a very old version of Fossil). If > you have a test case that demonstrates otherwise, I'd sure like to > see it. Ok, I'll see whether I can reproduce it again. Now, quick tests with both 1.24 indeed did not exhibit the behaviour. Perhaps I was still running 1.23 on one of the machines at that time. I'll keep an eye on it. Greetings, Stefan -- Stefan Bellon ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Official approved way of moving a repo?
On Tue, Jan 8, 2013 at 10:08 AM, Stefan Bellon wrote: > > In fact, this fossil behaviour puzzles me a lot because I tend to share > working copies via network share and at some point I end up having > _FOSSIL_ and .fslckout which are not in sync. Both windows and unix should look for both filenames. So you shouldn't ever run into a case where you end up with both (unless some of your machines are running a very old version of Fossil). If you have a test case that demonstrates otherwise, I'd sure like to see it. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Official approved way of moving a repo?
On Tue, Jan 8, 2013 at 4:08 PM, Stefan Bellon wrote: > In fact, this fossil behaviour puzzles me a lot because I tend to share > working copies via network share and at some point I end up having > _FOSSIL_ and .fslckout which are not in sync. Perhaps having a > configuration option to set the checkout filename would please all? > IN THEORY you could use this workaround: after opening from Windows, remove .fslckout. Your fossil binary on *nix will (i _think_) then see _FOSSIL_ and will (i think) use it. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Official approved way of moving a repo?
On Tue, 08 Jan, Richard Hipp wrote: > [...] On windows, the file is still called _FOSSIL_ because some > windows systems have issues with filenames that begin with ".". Is this really (still) the case? Subversion uses directories called .svn for years now. And the GnuWin32 toolchain uses files like .lesshst as well. It is true that you cannot create files and directories that start or end with a dot via the explorer, but it is possible via command line and via API functions. In fact, this fossil behaviour puzzles me a lot because I tend to share working copies via network share and at some point I end up having _FOSSIL_ and .fslckout which are not in sync. Perhaps having a configuration option to set the checkout filename would please all? Greetings, Stefan -- Stefan Bellon ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Official approved way of moving a repo?
On Tue, Jan 8, 2013 at 9:46 AM, Stephan Beal wrote: > > Be aware: that thread refers to a file named _FOSSIL_. That file is now > called .fslckout. > ... on non-windows systems. On windows, the file is still called _FOSSIL_ because some windows systems have issues with filenames that begin with ".". And _FOSSIL_ is recognized on all systems for backwards compatibility. There was another name used for this file at one point - but that other name turned out to be a mild profanity in Hungarian and hence was changed to ".fslckout". That other name is still recognized for backwards compatibility but is never generated. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Official approved way of moving a repo?
On Tue, Jan 8, 2013 at 1:55 PM, Martin Gagnon wrote: > > I haven't thought it through from a file integrity point of view but I'm > > looking for a way to do this given the repo is open and is in a new > > location. > > > > Also, by closing the repo, you will loose your stash and latest undo's > (if you have some) > True enough. Here's an old thread on the topic which might be helpful. i didn't read all the way through it, but it seems to be the same question and a workaround: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg06800.html Be aware: that thread refers to a file named _FOSSIL_. That file is now called .fslckout. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Official approved way of moving a repo?
On Tue, Jan 08, 2013 at 12:42:19PM +, John Long wrote: > On Tue, Jan 08, 2013 at 01:31:18PM +0100, Stephan Beal wrote: > > On Tue, Jan 8, 2013 at 1:22 PM, John Long wrote: > > > > > I just finished deleting a few dozen repos since I moved a bunch of source > > > code to another machine and fossil refused to like it. After that I found > > > a > > > discussion on the mailing lists about test-move-repository. Not a big deal > > > since this was all test stuff but I would like to know what the official > > > approved way is to let fossil know a repository has been moved. > > > > > > For example: > > > > > > old repo was in /home/user/code/project > > > > > > copied the project directory including the repo to > > > /newmachine/differentuser/programs/newplace > > > > > > > The easiest way, IMO, is: > > > > fossil close > > move repo file > > fossil open --keep /path/to/new/repo > > > > The --keep option keeps fossil from overwriting any changes you made > > between moving and opening the repo. > > Closing the repo isn't always going to be an option. For example when you > have to restore from a backup or are wiping a system to install a new > system you may not be able to find all the repos and close them. I am > working from backups in my example. fossil wouldn't let me open the repo. > > I haven't thought it through from a file integrity point of view but I'm > looking for a way to do this given the repo is open and is in a new > location. > Also, by closing the repo, you will loose your stash and latest undo's (if you have some) -- Martin G. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Official approved way of moving a repo?
On Tue, Jan 08, 2013 at 01:31:18PM +0100, Stephan Beal wrote: > On Tue, Jan 8, 2013 at 1:22 PM, John Long wrote: > > > I just finished deleting a few dozen repos since I moved a bunch of source > > code to another machine and fossil refused to like it. After that I found a > > discussion on the mailing lists about test-move-repository. Not a big deal > > since this was all test stuff but I would like to know what the official > > approved way is to let fossil know a repository has been moved. > > > > For example: > > > > old repo was in /home/user/code/project > > > > copied the project directory including the repo to > > /newmachine/differentuser/programs/newplace > > > > The easiest way, IMO, is: > > fossil close > move repo file > fossil open --keep /path/to/new/repo > > The --keep option keeps fossil from overwriting any changes you made > between moving and opening the repo. Closing the repo isn't always going to be an option. For example when you have to restore from a backup or are wiping a system to install a new system you may not be able to find all the repos and close them. I am working from backups in my example. fossil wouldn't let me open the repo. I haven't thought it through from a file integrity point of view but I'm looking for a way to do this given the repo is open and is in a new location. Thanks. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Official approved way of moving a repo?
On Tue, Jan 8, 2013 at 1:22 PM, John Long wrote: > I just finished deleting a few dozen repos since I moved a bunch of source > code to another machine and fossil refused to like it. After that I found a > discussion on the mailing lists about test-move-repository. Not a big deal > since this was all test stuff but I would like to know what the official > approved way is to let fossil know a repository has been moved. > > For example: > > old repo was in /home/user/code/project > > copied the project directory including the repo to > /newmachine/differentuser/programs/newplace > The easiest way, IMO, is: fossil close move repo file fossil open --keep /path/to/new/repo The --keep option keeps fossil from overwriting any changes you made between moving and opening the repo. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Official approved way of moving a repo?
I just finished deleting a few dozen repos since I moved a bunch of source code to another machine and fossil refused to like it. After that I found a discussion on the mailing lists about test-move-repository. Not a big deal since this was all test stuff but I would like to know what the official approved way is to let fossil know a repository has been moved. For example: old repo was in /home/user/code/project copied the project directory including the repo to /newmachine/differentuser/programs/newplace What command(s) should I use to tell fossil the repo now exists in /newmachine/differentuser/programs/newplace? Thanks /jl ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
