On 9/6/17, Thomas wrote:
>
> If I unshun
> a7ffc6f8bf1ed76651c14756a061d662f580ff4de43b49fa82d80a4b80f8434a now the
> next one to check in (run the check-in script) would cause all the other
> empty files to be distributed to everyone else, wouldn't they?
>
> Why are those not removed, by the way?
On 2017-09-06 23:45, Richard Hipp wrote:
On 9/6/17, Stephan Beal wrote:
i'm speculating, based on the fact that you're pulling "shun" info, that
you once shunned one of those files. ALL empty files have the same hash
code, so if you shunned one of them, you've shunned them all.
I was stumpe
On 9/6/17, Stephan Beal wrote:
>
> i'm speculating, based on the fact that you're pulling "shun" info, that
> you once shunned one of those files. ALL empty files have the same hash
> code, so if you shunned one of them, you've shunned them all.
>
I was stumped. Then I read Stephan's theory and
On Thu, Sep 7, 2017 at 12:29 AM, Thomas wrote:
> Hello,
>
> I got an issue with an empty file that's constantly being deleted whenever
> I run the checkin script after another contributor checked in using the
> same script.
>
> The script does:
> fossil addremove --dotfiles
> fossil update --forc
Hello,
I got an issue with an empty file that's constantly being deleted
whenever I run the checkin script after another contributor checked in
using the same script.
The script does:
fossil addremove --dotfiles
fossil update --force-missing
fossil configuration pull shun
fossil commit --allo
Hello,
I got an issue with an empty file that's constantly being deleted
whenever I run the checkin script after another contributor checked in
using the same script.
The script does:
fossil addremove --dotfiles
fossil update --force-missing
fossil configuration pull shun
fossil commit --allo
6 matches
Mail list logo
