Thus said Florian Balmer on Sat, 29 Oct 2016 09:32:25 +0200:
> * Clone the repository from the server to the client
> * Add and commit a lot of files (try the Fossil /src directory)
> * Add an unversioned file (I named it `home.wiki')
> * Run `fossil sync -u'
I tried this and it works fine for
This issue seems to be similar to what has been found with 'fossil cat',
and subsequently fixed:
http://www.fossil-scm.org/index.html/info/f2fc37c063af9fae
In brief, when the source-code contains CR/LF line-endings, 'fossil diff'
in non-console output (when run non-interactively) on Windows shows
Thus said arnoldemu on Sun, 30 Oct 2016 16:45:43 +0100:
> this showed DELETE of file from new location and REVERT of old
> location and changes showed this operation was successful. Please
> support wildcards for missing files :)
Seems to work for me:
$ ls
intlace.asm
On Sun, 30 Oct 2016 15:55:02 +0100 (CET)
arnoldemu wrote:
> So wildcards appear to apply to the files locally rather than those
> in the repository. Should wildcards apply to both locally and in the
> repository?
Locally as this matches the behavior of UNIX
On Sun, Oct 30, 2016 at 5:43 PM, arnoldemu wrote:
> I tested it on linux (ubuntu, bash shell) and it does expand it unless I
> surround it with quotes.
>
> without quotes:
>
That's because the shell leaves anything in quotes (mostly) alone. By
quoting it, you
This is fossil version 1.36 [65e69b8dd8] 2016-10-24 18:15:07 UTC
Compiled on Oct 29 2016 19:57:38 using msc-18.00 (32-bit)
SQLite 3.15.0 2016-10-14 10:20:30 707875582f
Schema version 2015-01-24
zlib 1.2.8, loaded 1.2.8
SSL (OpenSSL 1.0.2j 26 Sep 2016)
UNICODE_COMMAND_LINE
STATIC_BUILD
Just to
I tested the automatic expansion of wildcards on windows and linux.
Here is my program:
#include
#include
int main(int argc, char **argv)
{
int i;
for (i=0; i
On Sun, Oct 30, 2016 at 5:04 PM, arnoldemu wrote:
> Ok, I understand that wildcards are expanded by the shell but it would
> make it *SO* much easier to use if fossil could do some kind of pattern
> matching or use wildcards to allow me to revert a group of
Ok, I understand that wildcards are expanded by the shell but it would make it
*SO* much easier to use if fossil could do some kind of pattern matching or use
wildcards to allow me to revert a group of files.
It feels a little inconsistent to me that I can't use wildcards throughout. I
can
On Sun, Oct 30, 2016 at 4:45 PM, arnoldemu wrote:
> Hi,
>
> This is probably related to move and missing files in general.
>
> It's not possible to do a revert using a wildcard to revert multiple
> missing files. You have to specify them one by one.
>
Hi,
This is probably related to move and missing files in general.
It's not possible to do a revert using a wildcard to revert multiple missing
files. You have to specify them one by one.
For example:
I used mv to move some files:
intlace.asm
intlace.bat
intlace.bin
intlace.sh
I did not
Hi,
I found an unexpected inconsistency with fossil mv on files when using
wildcards.
I want to move 2 files into another directory:
itest.asm and itest.bin
Both files exist in the repository.
If both exist locally:
fossil mv itest.* newdir
then fossil will rename *both*. changes show both
BTW, There are around 400 warnings. I posted just a few of them.
So please compile with this patch to the makefile and visual studio 2015 with
the analyze option enabled to see them all.
A few more:
c:\users\kev\downloads\fossil-src-1.36\fossil-1.36\src\sqlite3.c(113673) :
warning C6239: ( &&
Steve, I agree with you it is confusing!
I have used fossil for over 2 years now (and I continue to use it because I
like it very much) but I haven't used the move operation much in that time and
each time I do use it the two step move is confusing.
I am used to other source control systems
On Fri, Oct 28, 2016 at 7:02 PM, Warren Young wrote:
> On Oct 28, 2016, at 3:45 AM, Karel Gardas wrote:
>>
>> make it more scale-able and allow its real usage also for projects of
>> bigger size.
>
> How many projects are there bigger than SQLite,
15 matches
Mail list logo