On 7/22/2014 08:38, Michai Ramakers wrote:
I was wondering how many of you use 'open --nested' to have nested workdirs?
Thanks to this thread, I became aware of open --nested, and promptly
found a use for it. So thank you. :)
Here's the problem that open --nested solved for us:
We keep tw
On 7/22/2014 9:38 AM, Michai Ramakers wrote:
I was wondering how many of you use 'open --nested' to have nested workdirs?
Tcl nests whatever repositories you want checked out into subdirectories
of pkgs. Each nested repository is expected to further nest the
Tclconfig repository (itcl and th
On 22 July 2014 21:18, Matt Welland wrote:
> We are using -nested very successfully to break a large area of related but
> mostly independent sub-areas into multiple fossils. I'm very happy with it.
>
> BTW, the whole reason why the modern SCM approach used by fossil, git etc.
> is so powerful is
We are using -nested very successfully to break a large area of related but
mostly independent sub-areas into multiple fossils. I'm very happy with it.
BTW, the whole reason why the modern SCM approach used by fossil, git etc.
is so powerful is because the number of degrees of freedom were reduced
NOTE: In Unix there is the handy shortcut that you can leave off the target
location:
ln -s foo/bar
will create the link:
bar -> foo/bar
Quite handy and yet another reason for the parameter ordering used on
Linux/Unix.
On Tue, Jul 22, 2014 at 9:46 AM, Warren Young wrote:
> On 7/22/2014 10:4
On 7/22/2014 10:43, Warren Young wrote:
the mklink command has its options in reverse order
I shouldn't say "option" here. I mean the two path names you have to
give to both mklink and ln:
$ ln source symlink-target
C:\> mklink symlink-target source
On 7/22/2014 10:22, Ron W wrote:
Yes, I know that modern versions of Windows
support symlinks, but I was getting eros from the command so I just did
nested check outs instead.
Native symlinks on Windows are a mess.
First, the mklink command has its options in reverse order as compared
to ln(
On Tue, Jul 22, 2014 at 10:38 AM, Michai Ramakers
wrote:
> Hello,
>
> I was wondering how many of you use 'open --nested' to have nested
> workdirs?
>
I have used it on MS Windows on a few occasions where I might otherwise
have used symbolic links (Yes, I know that modern versions of Windows
sup
On Tue, Jul 22, 2014 at 4:38 PM, Michai Ramakers
wrote:
> I was wondering how many of you use 'open --nested' to have nested
> workdirs?
>
nope
> A long time ago I asked here how/why/if people divided multiple-target
> project-trees into repos; some (like me) use one big repo for all, and
> so
Hello,
I was wondering how many of you use 'open --nested' to have nested workdirs?
A bit of background:
A long time ago I asked here how/why/if people divided multiple-target
project-trees into repos; some (like me) use one big repo for all, and
some use many small repos.
So this is not a real
10 matches
Mail list logo
