2014-04-09 18:07 GMT+02:00 j. van den hoff :
> this behaviour seems buggy (or I miss some crucial point):
>
> under certain circumstances `fossil extras' and `fossil changes' don't
> report the file name of the affected files correctly. specifically from
> within
> a subdir, if the behaviour is tri
Hello,
It isn't possible to do fossil sync/pull/push --once anymore after
cloning a repository if the Fossil user does not match the local user
due to this change:
http://www.fossil-scm.org/index.html/info/64aa75260f48781c
This is what happens...
Here, the new URL is properly parsed an
On Wed, Apr 9, 2014 at 6:07 PM, j. van den hoff
wrote:
> under MacOS
>
> can someone confirm this? bug or non-bug? any ideas?
Confirmed on Linux in trunk:
[stephan@host:~/cvs/fossil/x]$ touch abc def.txt; mkdir abcdir
[stephan@host:~/cvs/fossil/x]$ f-new ../x.fsl
Created repository: ../x.fsl
se
Hello,
On 9 April 2014 18:07, j. van den hoff wrote:
>
> 8<
> mkdir tmp
> cd tmp
> touch abc def.txt
> mkdir abcdir
>
> fossil init db.fossil
> fossil open db.fossil
>
> fossil extras #`abc' correctly reported here...
> cd abcdir
> fossil extras #... but not here (
this behaviour seems buggy (or I miss some crucial point):
under certain circumstances `fossil extras' and `fossil changes' don't
report the file name of the affected files correctly. specifically from
within
a subdir, if the behaviour is triggered, fossil reports only the dirname,
i.e.
`
5 matches
Mail list logo