I think the change at
http://www.fossil-scm.org/fossil/ci/82979bc210?sbs=1might help too.
On Mon, Nov 28, 2011 at 1:01 PM, Ron Wilson wrote:
> On Fri, Nov 25, 2011 at 5:02 PM, Barry Kauler wrote:
> > My question is, if I have 'allow-symlinks' in the online repository,
> > shouldn't the clone op
On Fri, Nov 25, 2011 at 5:02 PM, Barry Kauler wrote:
> My question is, if I have 'allow-symlinks' in the online repository,
> shouldn't the clone operation inherit that? To not inherit it, seems
> to defeat the purpose.
Try:
fossil configuration pull woof2.fossil
after you do the clone.
___
On Sat, 26 Nov 2011 13:16:27 + Ben Summers wrote:
> "allow-symlinks" is not a versionable setting. Is there a reason why
> it shouldn't be? It sounds like it should be as it affects the
> checked out files.
It should be, yes. The reason is that it's currently non-versionable is
that I started
On 25 Nov 2011, at 22:02, Barry Kauler wrote:
> Hi guys,
> I am just getting started with Fossil again, after a brief fling back
> in late 2009. I was very impressed, but my project has lots of
> symlinks, which is what brought me to a halt before.
>
> When I created my "woof2" repository, I tic
Hi guys,
I am just getting started with Fossil again, after a brief fling back
in late 2009. I was very impressed, but my project has lots of
symlinks, which is what brought me to a halt before.
When I created my "woof2" repository, I ticked "allow-symlinks". All
seemed well, however when I did a
5 matches
Mail list logo
