On 9/7/17, BohwaZ wrote:
>
> I managed to reproduce it on a different repo, it works if you change
> the file (like you did), but if you just add a file that didn't change
> it fails:
Thanks for the additional information. I think I have now found and
fixed the problem. Try out the latest trunk
Kia ora,
I managed to reproduce it on a different repo, it works if you change
the file (like you did), but if you just add a file that didn't change
it fails:
% echo one > test.txt
% fossil uv add test.txt
% fossil uv sync -v
Bytes Cards Artifacts Deltas
Sent:
On 9/7/17, Warren Young wrote:
>
> The globbing rules are completely reverse-engineered and documented here:
>
>https://www.fossil-scm.org/fossil/doc/trunk/www/globs.md
>
> What more is needed?
Thanks. I didn't realize that document existed. Maybe I need to add
hyperlinks that point to the
On 9/7/17, Warren Young wrote:
>
> The globbing rules are completely reverse-engineered and documented here:
>
>https://www.fossil-scm.org/fossil/doc/trunk/www/globs.md
>
> What more is needed?
Thanks. I didn't realize that document existed. Maybe I need to add
hyperlinks that point to the
On 2017-09-07 23:32, Ron W wrote:
The other type of empty files (actually, just one single file) is used
for a test case to check how one part of the project gracefully handles
an empty file. So, this file is actually not created by every
contributor individually according to thei
On 2017-09-07 23:21, Richard Hipp wrote:
On 9/7/17, Thomas wrote:
Shunning is not a way to proactively prevent files from being added to
a project. I think you probably want to use the ignore-glob. See
https://www.fossil-scm.org/fossil/help?cmd=ignore-glob for the
documentation on the ignor
On Thu, Sep 7, 2017 at 5:25 PM,
wrote:
> The other type of empty files (actually, just one single file) is used
> for a test case to check how one part of the project gracefully handles
> an empty file. So, this file is actually not created by every
> contributor individually according to their p
On Sep 7, 2017, at 4:21 PM, Richard Hipp wrote:
>
> https://www.fossil-scm.org/fossil/help?cmd=ignore-glob for the
> documentation on the ignore-glob setting. I confess that the
> documentation is a bit thin at the moment and needs enhancement, but
> it is what we have for now.
The globbing rul
On 9/7/17, Thomas wrote:
>
> There's 3 folders in the project.
> a
> b
> c
>
> I can create a file a/x.ext (empty and file length of 0), which should
> not go into the repository. Because if it goes into the repository
> everyone else would get that file. The pure existence of that file
> changes
On 2017-09-07 22:49, Richard Hipp wrote:
On 9/7/17, Thomas wrote:
The SHA3 hash for an empty file is in the shun list. What is going to
happen if I remove this entry? Would all those "suppress warning" files
be distributed among the team, i.e. would I with my next checkin turn
off all warning
On 9/7/17, Thomas wrote:
>
> The SHA3 hash for an empty file is in the shun list. What is going to
> happen if I remove this entry? Would all those "suppress warning" files
> be distributed among the team, i.e. would I with my next checkin turn
> off all warning messages for everyone else?
I do n
On 2017-09-07 00:48, Richard Hipp wrote:
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 ar
On Thu, Sep 7, 2017 at 7:20 PM, Tony Papadimitriou wrote:
> OK, thanks.
>
> But, what would be wrong with using / which is closer semantically, and
> compatible to both Linux and Windows path syntax?
>
Just to avoid potential ambiguity and user confusion (because Unix users
expect / to mean some
OK, thanks.
But, what would be wrong with using / which is closer semantically, and
compatible to both Linux and Windows path syntax?
From: Stephan Beal
Sent: Thursday, September 07, 2017 7:46 PM
To: fossil-users
Subject: Re: [fossil-users] Is there a way to specify paths relative to
checkout
There's not currently, and if someone wants to implement it i would suggest
: as a prefix, since fossil does not allow : in file names (for Windows
compatibility).
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos,
and top-posting.
On Sep 7, 2017 18:43, "Ton
For example, assuming a checkout tree like this:
lib/file
a/b/c/d/e/f/g/h/j/file
and while inside the j subdirectory, I want to refer to lib/file by doing
something like:
fossil tim –p /lib/file
instead of
fossil tim –p ../../../../../../../../lib/file
(and not sure if I got the number of .
16 matches
Mail list logo