Eric e...@... writes:
:
Most native English speakers would not even have thought of using
fieldslist, and it sounds odd. I think fieldlist is correct, though I
might have chosen
fossil ticket fields
depending on the rest of the possible syntax.
Regards,
Eric
What about
It sounds very nice !!
-RR
2010/10/7 Wolfgang rat...@stumvolls.de:
Eric e...@... writes:
:
fossil ticket fields
depending on the rest of the possible syntax.
:
With checkin 3f06f272cd , i changed it to
fossil ticket list fields
and added
fossil ticket list reports
All
Hi all,
does any body know a solution to sync a repository automatically to more than
one remote repository? As I understand in the fossil software at the moment
there is only one remote-url?!
I've got a repo on a file server in the company net work, a clone on my
harddisk and one on a memory
Christian Busch busch.christ...@... writes:
One more idea for the fossil ticket add ...:
Is it possible to print a command with the UUID of the new ticket?
-Christian
:
I think, i'll should print a protocoll message like
ticket UUID changed/added/add failed/update failed
to stdout
Christian Busch busch.christ...@... writes:
Hi all,
does any body know a solution to sync a repository automatically to more than
one remote repository? As I
understand in the fossil software at the moment there is only one remote-url?!
I've got a repo on a file server in the company
On Thu, Oct 7, 2010 at 8:44 AM, Christian Busch busch.christ...@gmx.dewrote:
Hi all,
does any body know a solution to sync a repository automatically to more
than one remote repository? As I understand in the fossil software at the
moment there is only one remote-url?!
I've got a repo on a
Hello,
we had a computer with a clock problem (its clock showed the time as two hours
less, in the same timezone). At some point the 'trunk' last checkin was newer
than 'branch' checkin, and the user run in 'branch': fossil merge trunk
That ended up with all the changes from trunk ported, but
Eric e...@... writes:
:
fossil ticket fields
depending on the rest of the possible syntax.
:
With checkin 3f06f272cd , i changed it to
fossil ticket list fields
and added
fossil ticket list reports
All commands can be shortend, f.e. fossil l f is valid!
I assume you mean
Eric e...@... writes:
All commands can be shortend, f.e. fossil l f is valid!
I assume you mean
fossil tic l f
(because of timeline and tag)
E
You are right, i was foccused on implementing the ticket command, so
i've forgotten to name it in the command line :-(
best regards
Wolfgang rat...@... writes:
:
With checkin 3f06f272cd , i changed it to
fossil ticket list fields
and added
fossil ticket list reports
All commands can be shortend, f.e. fossil l f is valid!
The command is merged into the trunk.
= Ramdebugger can learn to fly, using ticket
On Thu, Oct 7, 2010 at 1:37 AM, Wolfgang rat...@stumvolls.de wrote:
Brian Smith br...@... writes:
:
TH1 usage: 'wikicontent WIKIPAGE_NAME FALLBACK_TEXT'
The command returns the contents of a wiki page (presently, only real
wiki pages, not embedded docs),
or FALLBACK_TEXT, if the page
Hello,
some here said that they want a tool to migrate the repository data from svn to
fossil. I wrote some very poor scripts that did the job for me; being as simple
as they are, they are not very generic but they may be easier to adapt than a
300 lines script.
The manual procedure I did:
- Get
Greetings!
Is it by design that passwords are stored unencrypted in the
database/repository? Specifically event.last-sync-pw.
Basically, I was trying to sync/pull from another team member using the
https protocol (his server was configured using apache cgi-bin). There was
an error during the
13 matches
Mail list logo
