On Tue, Feb 28, 2012 at 2:06 AM, Gour g...@atmarama.net wrote:
On Wed, 21 Dec 2011 12:25:19 -0500
Richard Hipp d...@sqlite.org wrote:
I fear to change it now, though, since it might really mess up people
who are used to the older style.
What about having something like:
fossil rm
On Tue, 28 Feb 2012 07:28:11 -0500
Richard Hipp d...@sqlite.org wrote:
Assuming we go with Fossil 2.0, can somebody propose a list of
interface changes that are needed. We don't want to repeat this
exercise if it can be avoided, so let's fix everything all at once.
Here's a start:
(1)
(1) fossil rm removes the files from the disk
(2) fossil mv renames the files on disk
(3) fossil settings crnl-glob **
(4) fossil update == fossil update current
(5) Unlimited undo (purgin old undos after a defined number of days)
(6) Explain in more detail the clock problems with the
On Tue, Feb 28, 2012 at 07:59, Ramon Ribó ram...@compassis.com wrote:
(1) fossil rm removes the files from the disk
(2) fossil mv renames the files on disk
(3) fossil settings crnl-glob **
(4) fossil update == fossil update current
(5) Unlimited undo (purgin old undos after a defined
On Tue, 28 Feb 2012 08:22:52 -0500
Leo Razoumov slonik...@gmail.com wrote:
(8) search through wiki pages, timeline, tickets (fossil-scm.org
branch exp-search [1] can be a good start)
Thank you for this one which I forgot to mention.
Sincerely,
Gour
--
Bewildered by the modes of material
On Tue, 28 Feb 2012 08:22:52 -0500
Leo Razoumov slonik...@gmail.com wrote:
(1) fossil rm removes the files from the disk
(2) fossil mv renames the files on disk
(3) fossil settings crnl-glob **
(4) fossil update == fossil update current
(5) Unlimited undo (purgin old undos after
(1) fossil rm removes the files from the disk
(2) fossil mv renames the files on disk
(3) fossil settings crnl-glob **
(4) fossil update == fossil update current
(5) Unlimited undo (purgin old undos after a defined number of days)
(6) Explain in more detail the clock problems with the
(1) fossil rm removes the files from the disk (2) fossil mv renames
the files on disk (3) fossil settings crnl-glob ** (4) fossil
update == fossil update current (5) Unlimited undo (purgin old undos
after a defined number of days) (6) Explain in more detail the clock
problems with
On Tue, Feb 28, 2012 at 08:22, Leo Razoumov slonik...@gmail.com wrote:
On Tue, Feb 28, 2012 at 07:59, Ramon Ribó ram...@compassis.com wrote:
(1) fossil rm removes the files from the disk
(2) fossil mv renames the files on disk
(3) fossil settings crnl-glob **
(4) fossil update == fossil
On Tue, 28 Feb 2012 14:47:00 +0100
Ramon Ribó ram...@compassis.com wrote:
[...]
(9) in the web page, possibility to mark branches as hidden. It will
be invisible in the timeline, branches section and files section
(files belonging only to hidden branches do not appear), unless a
special
On Wed, Feb 22, 2012 at 09:51:44AM +0100, Lluís Batlle i Rossell wrote:
Hello,
the fdiff page, patch mode, has HTML in it:
One example:
http://fossil-scm.org/index.html/fdiff?v1=806340fbc989550av2=f1d6ecabf37517e4patch
Isn't this problem important for a fix? I just write as a reminder...
In fact, the most annoying thing is to go to the files section and
find there files of several years ago that are not used anymore, or
that come from a mistake and they will remain there for years and
years more, making more difficult to review the other files.
The possibility of seeing only the
Hello,
at a closed leaf, I try:
fossil commit -b newbranch
and it tells me it can't work because the leaf is closed. SHouldn't it allow
committing to a new branch, from a closed leaf?
I had to remove the closed tag, and then branch.
Regards,
Lluís.
On Sun, Feb 26, 2012 at 11:21 AM, Gour g...@atmarama.net wrote:
On Sun, 26 Feb 2012 09:25:17 -0400
Chris Peachment ch...@ononbb.com wrote:
It looks to me like you could add a new field to the 'ticket' table,
The missing part is some way to pass the patient id to the report so
that it
I notice that, when I do fossil tag list, I get a list of all tags
including some that are non-propagating and closed. When I visit the
Tags screen from the web interface, I get what I'd expect to see when
listing tags. In particular, I have a tag for each released version,
including trunk. I
On Tue, Feb 28, 2012 at 9:19 PM, Ron Wilson ronw.m...@gmail.com wrote:
function as a link to the ticket. (This also works with embedded
document wiki pages, but updating embedded document pages with the
Fossil UI is not (yet) possible.)
FWIW: committing embedded docs via the JSON API is on
On Tue, Feb 28, 2012 at 9:40 PM, Nolan Darilek no...@thewordnerd.infowrote:
I'm wondering if what I get with fossil tag list might be brought in
sync with what I get from the web interface, since that is a more useful
list of tags for my project?
FWIW: the JSON API's tags interface offers
Huh, the fossil json tags list output seems inconsistent with these
other two:
{
fossil:aa55cf3aa6d4c74c781c1c8d2f9b0807c3a2740c,
timestamp:1330464343,
command:tag/list,
procTimeMs:1,
payload:{
raw:false,
includeTickets:false,
tags:[
On Tue, Feb 28, 2012 at 10:28 PM, Nolan Darilek no...@thewordnerd.infowrote:
Huh, the fossil json tags list output seems inconsistent with these
other two:
There are several options which
...
In particular, it lists wiki pages and events. I'm not sure how those
qualify as tags,
On 02/28/2012 03:36 PM, Stephan Beal wrote:
Amen. Maybe the JSON API should just support a dumbed-down tags
interface?
So it seems like the command line/web interface would have to use a
similar tag filter function, right? I mean, they're filtering out these
various tkt/wiki-/event- tags,
On Tue, Feb 28, 2012 at 01:51:29PM +0100, Gour wrote:
c) some aliasing mechanism so that user can create aliases for commands
invoked with common options, e.g, ability to define
cip = ci --private
Why not just use your shell's aliasing mechanism? For example, in a
Bourne compatible shell
On 2/28/2012 3:03 PM, Christopher Berardi wrote:
On Tue, Feb 28, 2012 at 01:51:29PM +0100, Gour wrote:
c) some aliasing mechanism so that user can create aliases for commands
invoked with common options, e.g, ability to define
cip = ci --private
Why not just use your shell's aliasing
On Tue, Feb 28, 2012 at 5:34 PM, Nolan Darilek no...@thewordnerd.info wrote:
followed the same code path, we'd be golden? Then all other interfaces be
they command line or JSON could require that you opt into whatever other tag
types you'd like.
This makes a lot of sense. Not automatically
At 03:04 PM 2/28/2012, Andreas Kupries wrote:
On 2/28/2012 3:03 PM, Christopher Berardi wrote:
On Tue, Feb 28, 2012 at 01:51:29PM +0100, Gour wrote:
c) some aliasing mechanism so that user can create aliases
for commands
invoked with common options, e.g, ability to define
cip = ci --private
On Tue, Feb 28, 2012 at 03:04:22PM -0800, Andreas Kupries wrote:
On 2/28/2012 3:03 PM, Christopher Berardi wrote:
On Tue, Feb 28, 2012 at 01:51:29PM +0100, Gour wrote:
c) some aliasing mechanism so that user can create aliases for commands
invoked with common options, e.g, ability to define
Not everyone uses Unix.
Are there Windows shells supporting aliases, outside of 'mingw/bash' ?
It's not free but I find JP Software's Take Command (TCMD) and Take
Command Console (TCC) indispensable. http://jpsoft.com
--
___
fossil-users mailing list
26 matches
Mail list logo
