Hi there,
Is there a fossil copy command? There's add, mv, rm but no cp?
It's a neat feature of subversion that you can copy a file either from the
current checked-out tree or from somewhere else in time and space from the
repository, thereby keeping a tracable history intact.
At the moment,
Hi all,
I've had the following error, and I don't know why and I don't know what it
really means and I don't know what to do about it! (yes, I really don't know!)
ERROR: [mefs1a.c] is different on disk compared to the repository
NOTICE: Repository version of [mefs1a.c] stored in
On Friday, August 24, 2012 6:57 PM, Richard Hipp wrote:
On Fri, Aug 24, 2012 at 12:45 PM, Andy Gibbs wrote:
Hi all,
I've had the following error, and I don't know why and I don't know what
it really means and I don't know what to do about it! (yes, I really
don't know!)
ERROR: [mefs1a.c
On Friday, August 24, 2012 10:35 PM, Richard Hipp wrote:
Fossil keeps track of which files have changed (by default) by looking
at the file size and the mtime. If neither the file size nor the mtime
have changed, fossil (by default) assumes that the content of the file
is also unchanged.
Hi,
I've recently had the following recurrent problem, namely that using fossil
sync or pull does not fully sync or pull from the server. This means
branches do get pulled (i.e. it doesn't seem to be an access restriction or
network problem), but notably the trunk does not, leaving it at an
Hi,
It seems (at least in v1.29) that it is not possible to do a fossil clone
with a username and password in the url and automatically remember the
password via a command line switch or other approach. What is really
interesting is that if you pipe y into the fossil clone command, then
On Thursday, August 28, 2014 6:41 AM, Andy Bradford wrote:
Thus said Andy Gibbs on Wed, 27 Aug 2014 18:58:21 +0200:
Is there a rationale behind this? Could there be a flag (e.g. -q /
--quiet would work!) that can do an automatic yes at this point?
I'm not sure about the rationale
On Thursday, January 22, 2015 11:16 AM, Jan Nijtmans wrote:
2015-01-22 10:43 GMT+01:00 Andy Gibbs andyg1...@hotmail.co.uk:
I am trying to create a commit without a parent, effectively so that I
can
create a separate stream inside my repository, in no way linked to trunk
and
all its branches
Hi,
Recently updated to fossil v1.30. I've noticed an unfortunate regression that
the fossil info command doesn't work with the -R switch.
I don't know whether this has been spotted by anyone else, but it doesn't seem
to be fixed in trunk. The following patch, partially reverting commit
Hi,
I am trying to create a commit without a parent, effectively so that I can
create a separate stream inside my repository, in no way linked to trunk and
all its branches.
I cannot find in the documentation how to do this, but I know that it is
possible because Jan Nijtmans has managed to
Hi,
As an admirer of DRH's code beauty stance, and having been kicking
around long enough to remember the markdown debacle, I was a little
surprised to see the s-word (!) appear in the fossil repository
(src/linenoise.c line 216).
Please don't misunderstand me, this is not being facetious, not
On Wednesday, December 02, 2015 4:40 PM, Andy Bradford wrote:
Thus said Andy Gibbs on Tue, 01 Dec 2015 19:14:13 +0100:
I am syncing with a single server, and I have made sure all the
clients have the same fossil version as the server (actually I've
upgraded them all to the latest
On Wednesday, December 02, 2015 5:06 PM, j. van den hoff wrote:
On Wed, 02 Dec 2015 16:56:35 +0100, Andy Gibbs
wrote:
I upgraded after the problem occurred. I was running 1.32 on the server
and 1.32 or 1.33 on the clients. All are running 1.34 now.
which at least means they were all post
On Thursday, December 03, 2015 5:21 AM, Andy Bradford wrote:
Thus said Andy Gibbs on Wed, 02 Dec 2015 16:56:35 +0100:
I can certainly let you know when (if?) it happens again. What can I
say about my usage patterns? ... I am certainly doing large check-ins,
for example, modifying 100s
On Thursday, December 03, 2015 9:48 AM, Andy Bradford wrote:
Thus said Andy Gibbs on Thu, 03 Dec 2015 08:56:42 +0100:
For reference, a single commit may lead to around 100 "round-trips" to
then sync with the server (assuming no commits coming back as well).
If you are usin
Hi,
I'm having an issue which recurs from time to time which is that "fossil
sync" doesn't actually do anything, by which I mean I get an output
something like this --
Sync with https://.
Round-trips: 1 Artifacts sent: 0 received: 0
Sync done, sent: 342250 bytes received: 376 ip:
On Tuesday, December 01, 2015 7:17 PM, Richard Hipp wrote:
On 12/1/15, Andy Gibbs wrote:
Hi,
I'm having an issue which recurs from time to time which is that "fossil
sync" doesn't actually do anything,
deleting the cloned repository and cloning again "fixes" the
On Fri, May 27, 2016 at 10:00 PM, Stephan Beal wrote:
> On Fri, May 27, 2016 at 6:39 PM, Andy Gibbs wrote:
>
>>File 3rdparty/chromium/third_party/sqlite/sqlite-src-3080704/manifest -
>> part of check-in [079a920cf4] at 2016-03-13 00:00:00 on branch trunk - **
>> mess
Hi,
I've just had a very, very odd experience with fossil. I'm running version
1.34.
Let me first explain what I have done.
I cloned a respository off our server. I then went into the clone's web UI
and disabled the auto-sync feature. I then made 7 commits, the first of
which caused a
alid check-in -- isn't that right? But how can I fix it?
Thanks again for your help in my hour of need :o)
Andy
- Original Message -
From: "Andy Gibbs" <andyg1...@hotmail.co.uk>
To: <fossil-users@lists.fossil-scm.org>
Sent: Friday, May 27, 2016 6:26 PM
Subject: W
20 matches
Mail list logo
