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
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?
In my case, there is no server used, because this is private work that I
Suppose it's Monday morning (like...5 minutes ago) and you committed all
your changes on Friday afternoon. You come in on Monday and use the
handy `fossil diff --tk` feature to see if you left anything uncommitted
last week.
When there are no outstanding changes and you `fossil diff --tk`, it
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. Correct?
From: Tony Papadimitriou
Sent: Monday, October 27, 2014 1:48 PM
New test version contained in branch: tk-diff-viewer, behaves in the
following way:
http://fossil-scm.org/index.html/info/cbd4dca6807d95d73c22cb02893887efc1b51655
When there are no changes, the GUI opens with void differences and a
message in a window informs the user: No changes. In this way,
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 8:10 AM, Sean Woods s...@seanwoods.com wrote:
Suppose it's Monday morning (like...5 minutes ago) and you committed all
your changes on Friday afternoon. You come in on Monday and use the
handy `fossil diff --tk` feature to see if you left anything uncommitted
last
On Mon, Oct 27, 2014, at 08:25 AM, Ramon Ribó wrote:
New test version contained in branch: tk-diff-viewer, behaves in the
following way:
http://fossil-scm.org/index.html/info/cbd4dca6807d95d73c22cb02893887efc1b51655
When there are no changes, the GUI opens with void differences and a
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:
Hello,
Parsing of contact information in git export is totally broken. For
example, if your contact information in fossil is Tomasz Konojacki
m...@xenu.tk, it will be exported to git as Tomasz Kon m...@xenu.tk,
when e-mail is longer than name results are even more bizarre.
Patch is located at
On Mon, Oct 27, 2014 at 7:38 PM, Tomasz Konojacki m...@xenu.tk wrote:
Parsing of contact information in git export is totally broken. For
example, if your contact information in fossil is Tomasz Konojacki
m...@xenu.tk, it will be exported to git as Tomasz Kon m...@xenu.tk,
when e-mail is
19 matches
Mail list logo
