Any improvement to the handling of symlinks gets my vote!
../Dave
On 7 May 2015 at 23:25, Abilio Marques wrote:
> +1. Been there, two times just in the last week (I need to sleep better).
>
> On Thu, May 7, 2015 at 7:51 PM, Andy Goth wrote:
>
>> I propose extending [fossil changes] to report w
+1. Been there, two times just in the last week (I need to sleep better).
On Thu, May 7, 2015 at 7:51 PM, Andy Goth wrote:
> I propose extending [fossil changes] to report when a file's execute bit
> has changed or it has become a symlink or ceased to be a symlink.
>
> For various annoying reaso
On my previous email I said I was looking for a feature in the help. While
being at it, I found out these two details that I want to report.
But first, I want to say something about the help/documentation. One of the
things I LOVE about fossil is the simplicity. No weird, ultra-hidden
cryptic comm
T
his is a thing I normally go through, and I believe is a silly question,
but I've read the entire help once again looking for it, and didn't find
it. Sometimes I do things like:
$fossil update d04e
UPDATE test.txt
---
On 5/7/2015 7:33 PM, Andy Goth wrote:
> When a file becomes a symlink, nothing is said at all.
Actually, I'm not entirely sure this is always the case. I have one
repository where making a non-executable file into a symlink resulted in
"execute permisssion cleared" but another repository where it
When a symlink turns into an ordinary file, the Fossil change listing
says "execute permission cleared". When a symlink is replaced with a
file that's also executable, Fossil says "execute permission set". When
a file becomes a symlink, nothing is said at all.
Fossil ought to report symlink chan
I propose extending [fossil changes] to report when a file's execute bit
has changed or it has become a symlink or ceased to be a symlink.
For various annoying reasons, many times I've unwittingly checked in a
bunch of execute or symlink brokenness, sometimes not discovering it
until much later.
On Thu, May 7, 2015 at 5:39 AM, Alaric Snell-Pym
wrote:
>
> For various reasons, I'd like to split the wiki out of a repo I have
> into a fresh new repo of its own. I'm guessing I can do something like a
> fossil deconstruct, delete anything that's not a wiki-change artifact,
> and then reconstru
For various reasons, I'd like to split the wiki out of a repo I have
into a fresh new repo of its own. I'm guessing I can do something like a
fossil deconstruct, delete anything that's not a wiki-change artifact,
and then reconstruct the result.
1) Would that work?
2) How do I reliably tell what
9 matches
Mail list logo
