> 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, it is
> possible to use the new commands of the interface like: "Older
> vers
On Mon, Oct 27, 2014 at 7:38 PM, Tomasz Konojacki wrote:
> Parsing of contact information in git export is totally broken. For
> example, if your contact information in fossil is "Tomasz Konojacki
> ", it will be exported to git as "Tomasz Kon ",
> when e-mail is longer than name results are even
Hello,
Parsing of contact information in git export is totally broken. For
example, if your contact information in fossil is "Tomasz Konojacki
", it will be exported to git as "Tomasz Kon ",
when e-mail is longer than name results are even more bizarre.
Patch is located at http://xenu.tk/fossil.p
> Message: 7
> Date: 27 Oct 2014 09:50:39 -0600
> From: "Andy Bradford"
> To: "Tony Papadimitriou"
> Cc: Fossil SCM user's discussion
> Subject: Re: [fossil-users] FOSSIL ALL
> Message-ID: <20141027095039.14517.qm...@angmar.bradfordfamily.org>
>
> Thus said "Tony Papadimitriou" on Mon, 27 Oct
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 fil
On Mon, Oct 27, 2014 at 2:44 PM, Richard Hipp wrote:
> (1) Run "fossil all setting autosync off".
> (2) Make copies of all repos onto your thumb drive.
> (3) For each working check-out:
> (3a) "fossil remote file:/path/to/repo/on/thumb/drive"
> ...
> Then take the thumb drive home and do "fossil
On Mon, Oct 27, 2014 at 9:38 AM, Sean Woods 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 myself so m
On Mon, Oct 27, 2014 at 9:30 AM, Tony Papadimitriou 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 (Jan except
On Mon, Oct 27, 2014 at 6:58 AM, Tony Papadimitriou
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 add my tw
I use mostly Windows, but every so often I open the repo on a Linux box (but I
can do without Linux for now).
From: Richard Hipp
Sent: Monday, October 27, 2014 3:13 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL ALL
On Mon, Oct 27, 2014 at 6:58 AM, Tony Papadimitrio
On Mon, Oct 27, 2014 at 6:58 AM, Tony Papadimitriou 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 about how
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 8:10 AM, Sean Woods 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 week.
>
Clearly p
On Mon, Oct 27, 2014 at 8:30 AM, Stephan Beal 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. Stephan is right
On Mon, Oct 27, 2014 at 7:48 AM, Tony Papadimitriou wrote:
>
> So, are you saying, that if I keep both repo versions (work and home) open
> all the time, and simply copy over (from the backup) the related fossil
> files, there won’t be any corruption on either site?
>
Correct. Just copy the *.f
On Mon, Oct 27, 2014 at 1:18 PM, Tony Papadimitriou wrote:
> 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
On Mon, Oct 27, 2014 at 12:48 PM, Tony Papadimitriou 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 command?
>
All
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,
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
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
jus
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 c
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
On Mon, Oct 27, 2014 at 6:58 AM, Tony Papadimitriou 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? Why do
On Mon, Oct 27, 2014 at 11:58 AM, Tony Papadimitriou wrote:
> /somepath/a.fossil
> /otherpath/b.fossil (OPEN)
>
That won't (or shouldn't) work because once a repo is closed it will (or
should) no longer show up in the 'all' list.
> And, how about a command to close all open repos at once, e.
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 explicit
25 matches
Mail list logo
