Hello,
I noticed that Fossil requires the user to run commands in a directory
whose path matches where the file was added in the repository:
0. The repository is C:\Projects\my.repo, and there is single project
in C:\Projects\Project1\
1. In C:\Projects, I run fossil add . to add the files
On Thu, 27 Oct 2011 12:24:26 +0200 Gilles gilles.gana...@free.fr
wrote:
Is there a way to run a command in any sub-directory below the
repository, so that I don't have to cd to the right sub-directory
before running a command?
First of all, there's a distinction between a repository (and
On Thu, 27 Oct 2011 13:00:36 +0200, Dmitry Chestnykh
dmi...@codingrobots.com wrote:
Fossil expects your current directory to be inside the root of the
working copy, i.e. the working copy directory itself or any other
directory under it in the hierarchy.
Thanks for the infos, but the issue I was
On Thu, 27 Oct 2011 13:30:38 +0200, Dmitry Chestnykh
dmi...@codingrobots.com wrote:
On Thu, 27 Oct 2011 13:21:38 +0200 Gilles gilles.gana...@free.fr
wrote:
C:\Projects\Project2fossil diff Project1/Form1.vb
C:\fossil.exe: file Project2/Project1/Form1.vb does not exist in
checkin:
On Thu, 27 Oct 2011 13:54:37 +0200 Gilles gilles.gana...@free.fr
wrote:
Yes, but I find it odd that Fossil expects the current directory to
match the path in the repository: After all, when running commands
that deal with the files in the repository, it shouldn't matter where
we are in the
On Thu, 27 Oct 2011 15:13:58 +0200, Dmitry Chestnykh
dmi...@codingrobots.com wrote:
As for why it works this way -- this is just convenient and familiar.
If Fossil worked with absolute paths instead of relative ones, it would
be inconvenient to work with.
Thanks for the explanation.
6 matches
Mail list logo
