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
directory "subdir", this will works.
$ mkdir subdir
$ mv dir subdir/
$ fossil mv dir subdir/dir
** Note: You have to "subdir/dir" for the destination argument.
Otherwise it will not do what you what, it will move all
files that is inside dir directly in subdir. (so it doesn't
use the same semantic as the unix "mv" command).
If you want to skip the unix "mv" command part and use "--hard", it will
move the directory on the filesystem, but the fossil part of the move
will fail.
Regards,
--
Martin G.
On Sun, May 06, 2018 at 03:33:28PM +0000, Dewey Hylton wrote:
> 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 function in fossil which was basically a wrapper
> around file renames would certainly make those operations
> easier.
>
> I've always just used this method:
>
> for F in file1 file2 file3 ; do
> move="mv dir1/${F} dir2/${F}"
> $move && fossil $move
> done
>
> Looping around output from 'find' can be used for larger
> numbers of files or those in several subdirectories.
>
> When I'm working on one of my own boxes that get my own
> environment setup, I use a shell function called "fmv"
> which does this for me.
>
> The end result appears to be what OP is looking for,
> though of course the hard work is performed in the shell.
>
> On Sun, May 6, 2018 at 12:40 AM Andy Bradford <amb-fos...@bradfords.org>
> wrote:
>
> > 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 example, this works fine:
> >
> > $ mkdir first
> > $ touch first/file
> > $ ./fossil add first/file
> > ADDED first/file
> > $ ./fossil ci -m go
> > New_Version:
> > 600ce3e31ee64a3ff98a9af360b50d5ca24323acac04ee25d26eee82de78fa58
> > $ ./fossil mv --hard first/file second/file
> > RENAME first/file second/file
> > MOVED_FILE /tmp/first/file
> > $ ./fossil ci -m again
> > New_Version:
> > 5107ce9a7299518f44799149094ace083f7cec994578d429ca94897e3b09e395
> > $ ls first
> > $ ls second
> > file
> >
> > Andy
> > --
> > TAI64 timestamp: 400000005aee8760
> >
> >
> > _______________________________________________
> > fossil-users mailing list
> > fossil-users@lists.fossil-scm.org
> > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> >
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
