Le 2011-06-12 à 09:30, Stephan Beal <[email protected]> a écrit :
>
>
> On Sun, Jun 12, 2011 at 12:36 PM, David Bovill <[email protected]> wrote:
> Now that's interesting - so using nesting it should be possible to nicely
> work with shared components for multiple projects. A set up like this should
> be possible:
>
> You can have one folder with all the shared components, each component in
> it's own folder and versioned as a separate Fossil project, then for each
> application you work on you just check out the component into a subfolder of
> the project to keep all the components in sync.
>
> In that case, the top-level dir cannot be a fossil repo itself unless you do
> a bit of manual directory moving after creating the repo. Here's what happens
> when you try to open a sub-repo:
>
> ($PWD is a fossil repo here, btw)
>
> [stephan@cheyenne:~/cvs/fossil/cpdo]$ mkdir foo
> [stephan@cheyenne:~/cvs/fossil/cpdo]$ cd foo
> [stephan@cheyenne:~/cvs/fossil/cpdo/foo]$ f new ../../foo.fsl
> project-id: 80f6f77061933b7fb47867d08fd3a1e1af4b7f37
> ...
> [stephan@cheyenne:~/cvs/fossil/cpdo/foo]$ f open ../../foo.fsl
> f: already within an open tree rooted at /home/stephan/cvs/fossil/cpdo/
>
It's not the purpose of the --nested option of the open command?
--
Martin
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
