On Thu, 28 May 2015 23:29:14 +0200, j. van den hoff
veedeeh...@googlemail.com wrote:
On Thu, 28 May 2015 23:14:30 +0200, Ron W ronw.m...@gmail.com wrote:
On Thu, May 28, 2015 at 5:09 PM, j. van den hoff
veedeeh...@googlemail.com
wrote:
On Thu, 28 May 2015 22:47:32 +0200, Ron W
On Thu, May 28, 2015 at 2:56 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
So perhaps something similar like:
fossil branch mv BRANCH-NAME BASIS
I think fossil branch mv BASIS BRANCH-NAME is more intuitive (also
consistent with fossil mv OLDNAME NEWNAME)
On Thu, May 28, 2015 at 1:50 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
It is possible. I've done it. It just takes a strong understanding of
how propagating tags works and requires multiple commands with just the
right types of tags. There is not yet a single command that
On Thu, 28 May 2015 22:21:19 +0200, Ron W ronw.m...@gmail.com wrote:
On Thu, May 28, 2015 at 2:56 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
So perhaps something similar like:
fossil branch mv BRANCH-NAME BASIS
I think fossil branch mv BASIS BRANCH-NAME is more intuitive (also
On 5/28/15, jungle Boogie jungleboog...@gmail.com wrote:
Hello All,
I follow and update from trunk pretty regularly...this is how I notice
those harmless compiler warnings from time-to-time. I update on a few
different machines, too, so I don't know how I would have made this
mistake on
Thus said Ron W on Thu, 28 May 2015 11:43:07 -0400:
fossil tag cancel --raw 'branch' 53c9207df8 ramo
fossil tag cancel --raw sym-trunk 53c9207df8
fossil tag add --raw --propagate 'branch' 53c9207df8 ramo
fossil tag add --raw --propagate 'sym-ramo' 53c9207df8
Yes,
Hello All,
I follow and update from trunk pretty regularly...this is how I notice
those harmless compiler warnings from time-to-time. I update on a few
different machines, too, so I don't know how I would have made this
mistake on multiple machines.
For some reason, my fossil thinks I'm in this
Thus said paul on Thu, 28 May 2015 16:57:57 +0100:
I'm don't think it's possible to use the command line for this.
It is possible. I've done it. It just takes a strong understanding of
how propagating tags works and requires multiple commands with just the
right types of tags. There is
Thus said Richard Hipp on Thu, 28 May 2015 12:31:06 -0400:
Not strictly true, but true enough in practice. Perhaps it would be
worthwhile to add a new command-line way of moving a check-in to a new
branch. Suggested syntax, anyone?
``fossil branch new'' almost does what we want but it
Thus said Richard Hipp on Thu, 28 May 2015 12:31:06 -0400:
Not strictly true, but true enough in practice. Perhaps it would be
worthwhile to add a new command-line way of moving a check-in to a new
branch. Suggested syntax, anyone?
What if instead of a new addition to ``fossil branch''
On Tue, May 26, 2015 at 12:57 PM, Richard Hipp d...@sqlite.org wrote:
How long does this take:
fossil commit --dryrun -f -m 'not a real commit'
Here it is:
fossil commit --dry-run -f -m 'not a real commit' 24,79s user 6,26s
system 63% cpu 48,602 total
What if you first do:
fossil
[Default] On Thu, 28 May 2015 14:18:55 +0200, Luca Ferrari
fluca1...@infinito.it wrote:
Hi all,
I've another couple of questions: the first is that I noted that the
timeline is reporting time in UTC, while my computer is using
TZ='Europe/Rome'. I suspect this depends on the sqlite
On 5/28/15, Luca Ferrari fluca1...@infinito.it wrote:
On Tue, May 26, 2015 at 6:14 PM, Ron W ronw.m...@gmail.com wrote:
As I understand it, you need to add 2 tags: branch=mybranch and
sym-mybranch
Uhm..I've done a few experiments and apparently the following is not
having any effect:
Use
On Thu, May 28, 2015 at 3:26 PM, Richard Hipp d...@sqlite.org wrote:
Use the web interface. Visit the page that describes the check-in you
want to move and click on the edit link. Then select Make this
check-in the start of a new branch named and enter the new branch
name. Then press Apply
Hi all,
I've another couple of questions: the first is that I noted that the
timeline is reporting time in UTC, while my computer is using
TZ='Europe/Rome'. I suspect this depends on the sqlite configuration,
but I don't know how to set it up right.
The second question, that has been forgiven in
On Thu, May 28, 2015 at 8:31 AM, Luca Ferrari fluca1...@infinito.it wrote:
On Tue, May 26, 2015 at 6:14 PM, Ron W ronw.m...@gmail.com wrote:
As I understand it, you need to add 2 tags: branch=mybranch and
sym-mybranch
Uhm..I've done a few experiments and apparently the following is not
On 28/05/15 17:31, Richard Hipp wrote:
Not strictly true, but true enough in practice. Perhaps it would be
worthwhile to add a new command-line way of moving a check-in to a new
branch. Suggested syntax, anyone?
I wanted to do it through a script, rather than typing commands
manually. When
On 5/28/15, paul pault.eg...@gmail.com wrote:
On 28/05/15 17:31, Richard Hipp wrote:
Not strictly true, but true enough in practice. Perhaps it would be
worthwhile to add a new command-line way of moving a check-in to a new
branch. Suggested syntax, anyone?
I wanted to do it through a
(Wed, 27 May 14:03) Warren Young:
On May 23, 2015, at 1:25 PM, Svyatoslav Mishyn j...@openmailbox.org wrote:
/tmp: wget -S http://localhost:8080/reports
--2015-05-23 21:42:12-- http://localhost:8080/reports
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost
On 5/28/15, Svyatoslav Mishyn j...@openmailbox.org wrote:
(Wed, 27 May 14:03) Warren Young:
On May 23, 2015, at 1:25 PM, Svyatoslav Mishyn j...@openmailbox.org
wrote:
/tmp: wget -S http://localhost:8080/reports
--2015-05-23 21:42:12-- http://localhost:8080/reports
Resolving localhost
20 matches
Mail list logo
