Fossil mv *can* take a directory as argument and it will move every
files inside recursively. But the semantic is not exactly like the unix
"mv" command and it doesn't works with the "--hard" option (probably a
bug).
Example, if you have a directory "dir" and want to move it inside a new
Like Andy, I'm sure I've read that file names are what gets
tracked - and wasn't even aware anyone had worked on a
directory rename function ... At times when a project
grows, I do tend to create new subproject directories and
move existing files to those directories - and a directory
rename
The trunk version. The previous implementation is actually broken except
for file renaming.
Index: src/add.c
==
--- src/add.c
+++ src/add.c
@@ -859,10 +859,12 @@
int vid;
int moveFiles;
int dryRunFlag;
int softFlag;
Thus said Dingyuan Wang on Sun, 06 May 2018 00:37:23 +0800:
> The fossil mv command seems can't rename a directory.
I thought Fossil only tracked files (which is their complete path
relative to the repository checkout) and does not actually track
directories by themselves.
For
On 5/5/18, Dingyuan Wang wrote:
>
> The fossil mv command seems can't rename a directory.
I thought somebody had fixed that. But maybe not. What version are you using?
Renaming directories, or even files, is not something that I do very
often, as I find that it disrupts the
Hi,
The fossil mv command seems can't rename a directory.
eg.
`fossil mv --hard test test1` then `fossil status` will give
`RENAMEDtest1`.
Suppose that there is a file `a/test`. `fossil mv --hard a b` then
`fossil status` will give `MISSINGa/test`. `fossil commit` will
abort due to
6 matches
Mail list logo