We just happened to notice today that the list of repositories
maintained for the use of "fossil all" is (naturally) stored with
exactly the case that was used when each repository was mentioned to fossil.
Several folder names happened to be stored with different case than they
actually have
Thus said Richard Hipp on Fri, 19 Feb 2016 19:51:25 -0500:
> Again, I think the cleanup should be automatic.
It is for the most part automatic. It isn't automatic if the directory
still exists but is no longer a checkout. For example, I accidentally
opened up a repository in /tmp one time
On 2/19/2016 4:51 PM, Richard Hipp wrote:
On 2/19/16, Warren Young wrote:
Again, I think the cleanup should be automatic. But if you are still
having trouble the "fossil all ignore DIRECTORY" command should
manually remove the offending check-out from the list. Maybe the
On 2/19/16, Warren Young wrote:
> On Feb 19, 2016, at 3:06 AM, Tino Lange
> wrote:
>>
>> How can I get rid of an entry in "fossil all ls -c" for which the
>> checkout does not exist anymore? Do I need to fiddle with SQL?
>
> I think this happens
On Feb 19, 2016, at 3:06 AM, Tino Lange wrote:
>
> How can I get rid of an entry in "fossil all ls -c" for which the
> checkout does not exist anymore? Do I need to fiddle with SQL?
I think this happens when you nuke a fossil checkout (e.g. via rm -rf) without
> Should be automatic. When you do "fossil all ls -c", Fossil checks that
> each of the check-out directories exists, and removes any that do not
> exist from the list.
Thanks. The directory still exists (but with some other content now,
especially it has no .fslckout file)
So I'll move it
On Fri, Feb 19, 2016 at 11:06 AM, Tino Lange wrote:
> Hi Fossilers,
>
> There is no "fossil all remove".
> How can I get rid of an entry in "fossil all ls -c" for which the
> checkout does not exist anymore? Do I need to fiddle with SQL?
>
Fossil all recognizes
On 2/19/16, Tino Lange wrote:
> Hi Fossilers,
>
> There is no "fossil all remove".
> How can I get rid of an entry in "fossil all ls -c" for which the
> checkout does not exist anymore? Do I need to fiddle with SQL?
>
Should be automatic. When you do "fossil all
Hi Fossilers,
There is no "fossil all remove".
How can I get rid of an entry in "fossil all ls -c" for which the
checkout does not exist anymore? Do I need to fiddle with SQL?
Thanks
Tino
___
fossil-users mailing list
On Sat, Aug 1, 2015 at 4:36 AM, Gour g...@atmarama.net wrote:
Hello,
I had some recent changes of my OS-es (different distros, Linux, BSD…)
and now after settling on Debian (testing) I’d like to rebuild all my
Fossil repos, but encountered strange error:
gour@atmarama ~/r/e/fossil fossil
Scott Robison sc...@casaderobison.com
writes:
I'm doing some guess work here, but if the working directory is
/home/gour/repos/external/fossil then it can't be a valid repository.
Yes.
It seems that somewhere along the way /home/gour/repos/external/fossil
changed from being a repository to
(you know, those NAS/storage servers)?
From: Richard Hipp
Sent: Monday, October 27, 2014 3:44 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL ALL
On Mon, Oct 27, 2014 at 9:30 AM, Tony Papadimitriou to...@acm.org wrote:
I use mostly Windows, but every so often I open
I have several repos open at the same time, not always the same ones. Before I
swap computers (home = work) I would like to close all open repos on one
site, and take a backup to take to the other site.
But there is no easy way to find out which repos are currently open – so, I
must
On Mon, Oct 27, 2014 at 6:58 AM, Tony Papadimitriou to...@acm.org wrote:
I have several repos open at the same time, not always the same ones.
Before I swap computers (home = work) I would like to close all open
repos on one site, and take a backup to take to the other site.
Close them?
Actually, FOSSIL ALL LIST shows all repos, including the closed ones. If it
only showed the open ones, half of my problem would be solved (although a new
one would be created – how to see all repos installed on a given machine).
Regarding the rest of your comments please see my response to Dr
the previous version
goto LOOP
From: Richard Hipp
Sent: Monday, October 27, 2014 1:11 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL ALL
On Mon, Oct 27, 2014 at 6:58 AM, Tony Papadimitriou to...@acm.org wrote:
I have several repos open at the same time, not always the same
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL ALL
OK, maybe I have a misunderstanding of the need for close. What is it used
for? The claim by Stephan Beal that he hasn’t closed a repo more than 5 times
over many years makes me wonder why is there even a CLOSE command
On Mon, Oct 27, 2014 at 12:48 PM, Tony Papadimitriou to...@acm.org wrote:
OK, maybe I have a misunderstanding of the need for close. What is it
used for? The claim by Stephan Beal that he hasn’t closed a repo more than
5 times over many years makes me wonder why is there even a CLOSE
On Mon, Oct 27, 2014 at 8:30 AM, Stephan Beal sgb...@googlemail.com wrote:
If you are working by manually copying the repo dbs, then close is
probably a good thing to do, to avoid any side effects with blob IDs being
different between your checkout copies.
Yikes. I forgot about that.
On Mon, Oct 27, 2014 at 6:58 AM, Tony Papadimitriou to...@acm.org wrote:
I have several repos open at the same time, not always the same ones.
Before I swap computers (home = work) I would like to close all open
repos on one site, and take a backup to take to the other site.
Thinking
On Mon, Oct 27, 2014 at 6:58 AM, Tony Papadimitriou to...@acm.org
wrote:
I have several repos open at the same time, not always the same ones. Before
I swap computers (home = work) I would like to close all open repos on one
site, and take a backup to take to the other site.
I wanted to
On Mon, Oct 27, 2014 at 9:30 AM, Tony Papadimitriou to...@acm.org wrote:
I use mostly Windows, but every so often I open the repo on a Linux box
(but I can do without Linux for now).
Most thing we get working on Linux first, as that is the primary desktop
for most of the Fossil developers
On Mon, Oct 27, 2014 at 9:38 AM, Sean Woods s...@seanwoods.com wrote:
Also I saw in another thread the presence of a file:// URL scheme, but
saw no mention of it in the sync documentation. If it does exist
perhaps it's a solution for me.
I think it works. But to be clear, I don't use it
Thus said Tony Papadimitriou on Mon, 27 Oct 2014 14:18:04 +0200:
I guess the same scenario would be valid if one used a server but had
private branches. My understanding is that private branches do not
sync so the only way to move to another location is to move the whole
fossil file.
Message: 7
Date: 27 Oct 2014 09:50:39 -0600
From: Andy Bradford amb-fos...@bradfords.org
To: Tony Papadimitriou to...@acm.org
Cc: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] FOSSIL ALL
Message-ID: 20141027095039.14517.qm
It occurred to me that a good exercise for reacquainting myself with the
Fossil source tree (it's been awhile since DRH's presentation on same)
would be to add a [fossil all close] command. Plus I actually could use
such a thing right about now since I'm reorganizing repositories and
On 4/2/2014 11:42 PM, Joe Mistachkin wrote:
Andy Goth wrote:
I'm curious how a script could make use of [fossil extras] without
the benefit of the --showfile option.
The --showfile option is processed by the [fossil all] command, not
the [fossil extras] command, which basically explains the
Andy Goth wrote:
A possible compromise is to have [fossil all] only give --header to
[fossil extras] when [fossil all] was not given --showfile. I suggest
this on the presumption that any existing scripts that actually use
[fossil all extras] must use --showfile, because the output is
Andy Goth wrote:
Without the --showfile option, [fossil all extras] just prints filenames
relative to the directories in which the repositories were opened. It's
anyone's guess which files go with which directories and which
repositories. Additionally, --showfile prints the names of
On 4/2/2014 7:47 PM, Joe Mistachkin wrote:
Andy Goth wrote:
I prefer the behavior of [fossil all changes]. By default it prints
the names of both the repositories and directories with changes, plus
doesn't print anything for directories with no changes.
I would prefer to be consistent as
Andy Goth wrote:
I'm curious how a script could make use of [fossil extras] without the
benefit of the --showfile option.
The --showfile option is processed by the [fossil all] command, not the
[fossil extras] command, which basically explains the underlying issue...
The [fossil extras]
regarding this new command: as the help page correctly states Extreme
caution should be exercised with this command because its effects cannot
be undone. ...: this could cause real trouble for inexperienced users
presuming clean is some sort of innocuous tidy up like make clean.
would it
j. van den hoff wrote:
would it not be wise to change the default behavior to executing a dry-run
while delegating the actual action to something like fossil clean
--force? this also would bring the syntax more in line with `fossil
clean'.
The only thing 'fossil all clean' really
On Fri, 18 Oct 2013 09:26:59 +0200, Joe Mistachkin sql...@mistachkin.com
wrote:
j. van den hoff wrote:
would it not be wise to change the default behavior to executing a
dry-run
while delegating the actual action to something like fossil clean
--force? this also would bring the syntax
With the latest fossil trunk (This is fossil version 1.24 [bdbe6c74b8]
2012-10-30 18:14:27 UTC) fossil all rebuild is seg faulting for me.
fossil all rebuild
Segmentation fault (core dumped)
gdb is showing the below:
#0 collect_arguments (zArg=0x7f7f Address 0x7f7f out
of
Please try the latest and let me know whether or not the problem is fixed.
Tnx for the report.
On Tue, Oct 30, 2012 at 6:31 PM, James Turner ja...@calminferno.net wrote:
With the latest fossil trunk (This is fossil version 1.24 [bdbe6c74b8]
2012-10-30 18:14:27 UTC) fossil all rebuild is seg
Looks good. fossil all rebuild is working for me again. If it helps
explain anything, I'm running OpenBSD.
On Tue, Oct 30, 2012 at 08:11:53PM -0400, Richard Hipp wrote:
Please try the latest and let me know whether or not the problem is fixed.
Tnx for the report.
On Tue, Oct 30, 2012 at 6:31
On 31/10/2012, at 10:11 AM, Richard Hipp wrote:
Please try the latest and let me know whether or not the problem is fixed.
Tnx for the report.
Regarding your latest commit, I've run across this on 64 bit too.
The problem is the '0' at the end of the variable args.
Use NULL instead, otherwise
On Tue, Oct 30, 2012 at 8:18 PM, Steve Bennett ste...@workware.net.auwrote:
On 31/10/2012, at 10:11 AM, Richard Hipp wrote:
Please try the latest and let me know whether or not the problem is
fixed. Tnx for the report.
Regarding your latest commit, I've run across this on 64 bit too.
The
On Tue, Oct 30, 2012 at 08:22:25PM -0400, Richard Hipp wrote:
On Tue, Oct 30, 2012 at 8:18 PM, Steve Bennett ste...@workware.net.auwrote:
On 31/10/2012, at 10:11 AM, Richard Hipp wrote:
Please try the latest and let me know whether or not the problem is
fixed. Tnx for the report.
Hello,
Currently the help of fossil all says:
Respositories are automatically added to the set of known repositories
when one of the following commands are run against the repository: clone,
info, pull, push, or sync.
Would not be more logical that it where:
Respositories are
41 matches
Mail list logo