Wolfgang 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
Eric 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 reg
> Eric 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
Christian Busch 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 after comman
> Betreff: Re: [fossil-users] cmd line support for tickets
> It sounds very nice !!
>
> -RR
>
>
>
> 2010/10/7 Wolfgang :
> > Eric writes:
> >
> > :
> >>
> >> fossil ticket fields
> >>
> >> depending on the rest of
It sounds very nice !!
-RR
2010/10/7 Wolfgang :
> Eric 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
Eric 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!
best regards
Wolfgang
_
Eric 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
On Wed, October 6, 2010 at 12:25 pm, "Wolfgang" wrote:
> Ramon Ribó writes:
>
>>
>> what is your opinion between these two alternatives:?
>>
>> fossil.exe ticket fieldlist
>>
>> fossil.exe ticket fieldslist
>>
>
>
> I prefer the first on, but this might be influenced by my native
> language - ge
> A quick google search finds more fieldlist than fieldslist entries, so i
> tend to use fieldlist.
Then, if we have google veredict, it should be definitive!!!
RR
2010/10/6 Wolfgang :
> Ramon Ribó writes:
>
>>
>> what is your opinion between these two alternatives:?
>>
>> fossil.exe ticket fie
Ramon Ribó writes:
>
> what is your opinion between these two alternatives:?
>
> fossil.exe ticket fieldlist
>
> fossil.exe ticket fieldslist
>
I prefer the first on, but this might be influenced by my native
language - german.
A quick google search finds more fieldlist than fieldslist en
Nice work.
what is your opinion between these two alternatives:?
fossil.exe ticket fieldlist
fossil.exe ticket fieldslist
Compass Ing. y Sistemas Dr. Ramon Ribo
http://www.compassis.com ram...@compassis.com
c/ Tuset, 8 7-2 tel. +34 93 218 19 89
08006
Ramon Ribó writes:
:
> This new version looks very nice to be used by a GUI. A couple of comments:
>
> 1- fossil.exe ticket list
>
> Would it be better something like?:
>
> fossil.exe ticket fieldlist
I've changed the command to fieldlist
>
> 2- A proposal of small changes for t
Hello,
This new version looks very nice to be used by a GUI. A couple of comments:
1- fossil.exe ticket list
Would it be better something like?:
fossil.exe ticket fieldlist
Or similar? "fossil ticket list" looks like it is going to list all tickets
2- A proposal of small chang
Hi.
I've compiled:
This is fossil version [63d91f0b87] 2010-10-05 16:37:40 UTC
I've to do further tests, but at the moment it looks great.
Thanks.
Christian
Am 05.10.2010 20:22, schrieb wolfgang:
> Ramon Ribó writes:
>
>>> In the newest version, you can call the report by its name
>> This is
Ramon Ribó writes:
>
> > In the newest version, you can call the report by its name
>
> This is nice, but I was meaning that it was difficult for me to
> understand the help text. Maybe, it is difficult for someone else too.
OK, i've changed the default. I'm describing the title first. The nu
> In the newest version, you can call the report by its name :-)
This is nice, but I was meaning that it was difficult for me to
understand the help text. Maybe, it is difficult for someone else too.
>> 1- ...
>
> This doesn't help, because after reconfiguring, the columns in the gui do
> not
Ramon Ribó writes:
>
> Hi,
>
> It was not easy for me to discover that REPORTNR refers to one of
> the "report formats" listed in the "Tickets main menu page". I would
> explain it more detailed in the help, maybe using REPORT_FORMAT_NUMBER
> instead of REPORTNR
In the newest version, you
Hi,
It was not easy for me to discover that REPORTNR refers to one of
the "report formats" listed in the "Tickets main menu page". I would
explain it more detailed in the help, maybe using REPORT_FORMAT_NUMBER
instead of REPORTNR
At the same time, as the result of this command is a table, t
Ramon Ribó writes:
:
> > fossil.exe ticket show REPORTNR ?TICKETFILTER? ?-l|--limit LIMITCHAR?
>
> What is REPORTNR?
>
> > I think it should fulfill most requirements, even linking an external gui to
> > the fossil application
>
> How do you list all tickets that are not closed or fixed,
> fossil.exe ticket show REPORTNR ?TICKETFILTER? ?-l|--limit LIMITCHAR?
What is REPORTNR?
> I think it should fulfill most requirements, even linking an external gui to
> the fossil application
How do you list all tickets that are not closed or fixed, with its
basic data of:
TICKETUUID,title
Christian Busch writes:
:
> Will fossil have a kind of api or cmd line support for the ticket system
> in some future?
>
> The inverse problem will appear as well. Having all this tickets in
> fossil, I'd like to extract the information in some report format.
:
Hi
On branch wolfgangTicke
Christian Busch writes:
>
> That's looking perfect for me!
> I was about to "require" the add-comand, because this is the first thing
> I would need. Also the ability of checking and adding "own" defined
> field-value pairs would be very helpful.
>
> Anybody has further ideas to add?
>
That's looking perfect for me!
I was about to "require" the add-comand, because this is the first thing
I would need. Also the ability of checking and adding "own" defined
field-value pairs would be very helpful.
Anybody has further ideas to add?
Best regards,
Christian
Am 04.10.2010 20:46,
Lluís Batlle i Rossell writes:
:
> The interface for a script may be something like this, but if it is of any
> usage, I've been using for a long time a command line tool I wrote for ticket
> tracking [1]. There, adding a ticket or modifying a ticket created a tmp file
> and opened an editor wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/04/2010 12:14 PM, wolfgang wrote:
> If TICKETUUID is given on the commandline, only this ticket
> is listed, if the report delivers the uuid, otherwise the
> argument is ignored.
I'd say that this case should be handled b
wolfgang writes:
>
> Ramon Ribó writes:
>:
> > So, It would be enough for this application to have the possibility of
> changing the status of the ticket.
> >
> > It would be also nice to have a more ordered list of tickets with its id,
> comment and status so as to avoid parsing "fossil t
On Mon, Oct 04, 2010 at 04:53:03PM +, wolfgang wrote:
> Ramon Ribó writes:
>:
> > So, It would be enough for this application to have the possibility of
> changing the status of the ticket.
> >
> > It would be also nice to have a more ordered list of tickets with its id,
> comment and sta
Ramon Ribó writes:
:
> So, It would be enough for this application to have the possibility of
changing the status of the ticket.
>
> It would be also nice to have a more ordered list of tickets with its id,
comment and status so as to avoid parsing "fossil timeline -t t"
> RR2010/10/4 Richard
> Since tickets are configurable on a site-by-site basis, I is difficult to
imagine
> what a command-line interface to the ticketing system might look like. Do
you > have any suggestions?
Yes, I do.
I've developed a GUI for fossil (inside RamDebugger), that permits to select
an open ticket and a
On Mon, Oct 4, 2010 at 4:25 AM, Christian Busch wrote:
> Hi all,
>
> I'm evaluating fossil as a scm for the developement of testing software
> for embedded system testing. There will be a huge amount of test
> scripts and after a test run there might be a lot of found problems in
> the test scri
Hi all,
I'm evaluating fossil as a scm for the developement of testing software
for embedded system testing. There will be a huge amount of test
scripts and after a test run there might be a lot of found problems in
the test scripts. I'd like to issue tickets for all found 'open points'
in
32 matches
Mail list logo
