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
On Tue, Jan 8, 2013 at 1:22 PM, John Long codeb...@inbox.lv 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
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 codeb...@inbox.lv wrote:
I just finished deleting a few dozen repos since I moved a bunch of source
code to another machine
On Tue, Jan 8, 2013 at 1:55 PM, Martin Gagnon eme...@gmail.com 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
On Tue, Jan 8, 2013 at 9:46 AM, Stephan Beal sgb...@googlemail.com 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
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
On Tue, Jan 8, 2013 at 4:08 PM, Stefan Bellon sbel...@sbellon.de 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
On Tue, Jan 8, 2013 at 10:08 AM, Stefan Bellon sbel...@sbellon.de 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
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
9 matches
Mail list logo
