On Fri, Jan 25, 2013 at 9:21 AM, Александр Орефков oref...@gmail.comwrote:
need
fossil.res : $B\win\fossil.rc
Fixed, thanks!
http://fossil-scm.org/index.html/info/461a4d11d1
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
On Wed, 09 Jan 2013 12:10:35 +0100, Gilles
gilles.gana...@free.fr wrote:
Am I correct in understanding that this is the right way to proceed to
try some new code, and either save it (whether it works or not, just
as a track-record) or discard it?
I have another question: fossil branch ls lists
On Fri, Jan 25, 2013 at 11:59 AM, Gilles gilles.gana...@free.fr wrote:
I have another question: fossil branch ls lists branches available
in the repo, but is there a command to list all the files/revisions
that have been commited to the experimental branch?
There are two ways i know of to do
On Fri, 25 Jan 2013 12:28:25 +0100, Stephan Beal
sgb...@googlemail.com wrote:
There are two ways i know of to do that, but both show the files _in_ the
branch, whether or not they have been modified _in that branch_ since the
branch was created:
Thanks for the info.
I don't understand what you
On Fri, Jan 25, 2013 at 12:41 PM, Gilles gilles.gana...@free.fr wrote:
I don't understand what you mean by both show the files _in_ the
branch, whether or not they have been modified _in that branch_ since
the branch was created. Do you meant that they'll list all files in a
branch, even
On Fri, Jan 25, 2013 at 1:14 PM, Stephan Beal sgb...@googlemail.com wrote:
There is no equivalent of the /dir page for the CLI.
It appears that i lied, at least partially: Martin shows us the 'ls'
command (which is new to me!).
--
- stephan beal
http://wanderinghorse.net/home/stephan/
On Fri, Jan 25, 2013 at 1:11 PM, Martin Gagnon eme...@gmail.com wrote:
Is this a bug or I mis understand meaning of ?VERSION? for the ls command ?
FWIW: it appears to me that it does not react intuitively when given a
branch name as a version:
[stephan@host:~/cvs/fossil/fossil]$ fossil ls
On Fri, 25 Jan 2013 13:16:46 +0100, Stephan Beal
sgb...@googlemail.com wrote:
It appears that i lied, at least partially: Martin shows us the 'ls'
command (which is new to me!).
Thanks guys.
The json command doesn't exist in the Fossil I have (1.24
[0c65916136]):
===
[C:\]fossil json dir
On Fri, 25 Jan 2013 14:14:20 +0100, Gilles
gilles.gana...@free.fr wrote:
What about switching to another branch (eg. going from trunk to
experimental), and simply running fossil ls? Will that list the
revisions without touching the files in my work directory?
I notice that fossil update
On Fri, 25 Jan 2013 14:38:25 +0100, Gilles
gilles.gana...@free.fr wrote:
I notice that fossil update experimental -n doesn't say which work
files will be replaced by what's in the experimental branch in the
repo (1 file modified.):
===
UPDATE dummy.c
Great, then it seems like the easiest choice. My last concern is if
appending to a file using is portable enough on all platforms. I'll
make some experiments and let you know if I get some resuilts.
I made a ticket:
On Fri, Jan 25, 2013 at 2:59 AM, Gilles gilles.gana...@free.fr wrote:
On Wed, 09 Jan 2013 12:10:35 +0100, Gilles
gilles.gana...@free.fr wrote:
Am I correct in understanding that this is the right way to proceed to
try some new code, and either save it (whether it works or not, just
as a
On Fri, Jan 25, 2013 at 3:54 AM, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Jan 25, 2013 at 9:21 AM, Александр Орефков oref...@gmail.comwrote:
need
fossil.res : $B\win\fossil.rc
Fixed, thanks!
http://fossil-scm.org/index.html/info/461a4d11d1
I don't know about nmake syntax,
On Fri, Jan 25, 2013 at 10:45 PM, Martin Gagnon eme...@gmail.com wrote:
I don't know about nmake syntax, but other reference to B in Makefile.msc
use brackets.
e.g: $(B) instead of just $B
Good point - i was copy/pasting from an MSC user ;).
I know that () are needed in GNU and BSD
Works for me after parking my previous tweaks in a private branch and
updating to trunk. I did not exercise the $B question since I've been
following the path of least resistance and building in the win folder.
After opening a VS2010 32-bit command prompt and changing to the win
folder, nmake
I should mention that the pull issue for machine A disappeared after a new
commit was pushed to the server from machine B. Everything is back to normal
with the original affected repo.
Thanks,
Edward Blake
___
fossil-users mailing list
I wonder, how hard is to make some kind of fake server that to accept read/info
requests in protocols used in git|svn|cvs|bazaar|Hg, translate them to fossil
and then returns the response to the client (in particular to ohloh statistics
engine) using the respective protocol.
This server might
17 matches
Mail list logo
