(version 1.28)
The "fossil stash" command does not seem to understand "fossil mv".
When a stash is restored, the files are given their old names.
$ fossil new test.fossil
$ mkdir test
$ cd test
$ fossil open ../test.fossil
$ echo moo > file
$ fossil add file
$ fossil commit -m add
$ mv file fi
Ohhh, it's ok if you say so... I was worried about security issues, but I
didn't stop to think about them. I'll set it to 0 then.
Thanks!
On Mon, Mar 17, 2014 at 3:00 PM, Richard Hipp wrote:
>
>
>
> On Mon, Mar 17, 2014 at 3:27 PM, Abilio Marques
> wrote:
>
>> Hi,
>>
>> I'm trying to access m
On Mon, Mar 17, 2014 at 6:00 PM, Stephan Beal wrote:
> Obviously not a general-purpose solution, it just came up spontaneously
> when i didn't have emacs open to add the FIXME directly to some source code
> ;). i need to extend f-tag so that we can add multiple tags at a time, e.g.
> fixme + bgco
On Mon, Mar 17, 2014 at 6:38 PM, Ron Wilson wrote:
> Using Javascript, you could use a (Fossil) wiki page in place of the
> ticket comment field. Would probably have to use the JSON features that
> Stephan Beal added to Fossil a while ago. Still, it likely would not be as
> clean as the way ticke
On Mon, Mar 17, 2014 at 3:27 PM, Abilio Marques wrote:
> Hi,
>
> I'm trying to access my personal repo server running at home. I'm doing it
> from the office, behind a load balancer. If I login, I loose access after a
> while (asks me to login again). The only solution I've found is to set the
> "
Hi, all,
Here's a silly fossil trick you'll certainly never need to do...
observe the creation of delta- vs baseline manifests in the repository by
looking at historical checkin data... the larger (>10kb) checkins are
baselines. The others are deltas generated from (normally) the next-oldest
base
Hi,
I'm trying to access my personal repo server running at home. I'm doing it
from the office, behind a load balancer. If I login, I loose access after a
while (asks me to login again). The only solution I've found is to set the
"IP address terms used in login cookie" to 0, but is something I don
On Mon, Mar 17, 2014 at 12:52 PM, j. van den hoff wrote:
> nice. but unfortunately not quite what we need here (it'd be somewhat
> awkward to assign a jpeg image as the vaulue to the tag, e.g. ;-)).
>
> what do other people think: is someone else missing the ability to
> edit/modify ticket commen
On Mon, Mar 17, 2014 at 5:53 AM, j. van den hoff
wrote:
> I would hope that making this (retrospective modification/correction of
> ticket comments) is not really impossible in the current setup and that one
> of the core developers would look into this if his time permits: it is
> really a nuisan
On Mon, Mar 17, 2014 at 5:52 PM, j. van den hoff
wrote:
> nice. but unfortunately not quite what we need here (it'd be somewhat
> awkward to assign a jpeg image as the vaulue to the tag, e.g. ;-)).
>
Yeah, it's ugly and limited, but that particular fixme has a very low
priority (i accidentally im
I miss it as well, but I am a one-man show on my repos, so it is more of an
inconvenience than anything. I would love to have the ability to edit the
initial comment field, though. I have a bunch of tickets I was testing with
and like to clean up.
JR
On Mar 17, 2014 11:52 AM, "j. van den hoff"
wr
On Mon, Mar 17, 2014 at 9:52 AM, j. van den hoff
wrote:
> On Mon, 17 Mar 2014 17:21:04 +0100, Stephan Beal
> wrote:
>
> For those who don't need the full features of the ticketing system, i
>> think
>> i've discovered a new way to keep track of bugs: use a "fixme" tag.
>>
>> [stephan@host:~/cvs/
On Mon, 17 Mar 2014 17:21:04 +0100, Stephan Beal
wrote:
For those who don't need the full features of the ticketing system, i
think
i've discovered a new way to keep track of bugs: use a "fixme" tag.
[stephan@host:~/cvs/fossil/libfossil]$ f-tag -a 4b05c2c59fa6 -t fixme -v
"This artifact ca
On Mon, Mar 17, 2014 at 5:22 PM, wrote:
> It's nowhere near finished, but here's a github-simulating layout:
>
> http://fossil.include-once.org/hybrid7/
>
> Barely holds together, and it's not yet working in Firefox. But includes
> fx_search support, my th1x functions for the language bar and f
On Mon, Mar 17, 2014 at 5:22 PM, wrote:
> It's nowhere near finished, but here's a github-simulating layout:
>
> http://fossil.include-once.org/hybrid7/
>
>
Exceedingly cool :)
> Barely holds together, and it's not yet working in Firefox.
Nor Chrome - the labels on the menus on the right di
It's nowhere near finished, but here's a github-simulating layout:
http://fossil.include-once.org/hybrid7/
Barely holds together, and it's not yet working in Firefox. But includes
fx_search support, my th1x functions for the language bar and file box,
and comes with built-in code highlighting.
For those who don't need the full features of the ticketing system, i think
i've discovered a new way to keep track of bugs: use a "fixme" tag.
[stephan@host:~/cvs/fossil/libfossil]$ f-tag -a 4b05c2c59fa6 -t fixme -v
"This artifact causes an HTTP 500 in the /manifest page of the CGI demo. It
is a
On Mon, Mar 17, 2014 at 2:57 PM, j. van den hoff
wrote:
> the user is concerned it really has, apparently) serves well to get a
> timeline with clean checkin messages (one of them being that another
> checkin comment has been edited, I believe?).
>
Right.
> in any case, something like that woul
On Mon, 17 Mar 2014 14:50:56 +0100, Stephan Beal
wrote:
On Mon, Mar 17, 2014 at 2:40 PM, j. van den hoff
wrote:
personally, I think it is great, that checkin comments _can_ be edited
after the fact (contrary to some other DVCSes) --
Just to avoid any confusion from those who don't know t
On Mon, Mar 17, 2014 at 2:40 PM, j. van den hoff
wrote:
> personally, I think it is great, that checkin comments _can_ be edited
> after the fact (contrary to some other DVCSes) --
>
Just to avoid any confusion from those who don't know the difference: in
Fossil you can't actually edit anything a
On Mon, 17 Mar 2014 14:14:49 +0100, Doug Franklin
wrote:
On 2014-03-17 5:53, j. van den hoff wrote:
it is really a
nuisance to look at a seriously misleading/erroneous/misplaced ticket
comment (the more so, if it happens not to be the very last one) and not
being able to correct it.
I jus
On 2014-03-17 5:53, j. van den hoff wrote:
it is really a
nuisance to look at a seriously misleading/erroneous/misplaced ticket
comment (the more so, if it happens not to be the very last one) and not
being able to correct it.
I just close the broken ticket and start a new one. I even add a "
On Mon, 17 Mar 2014 09:32:49 +0100, Martijn Coppoolse
wrote:
On 15-3-2014 17:08, j. van den hoff wrote:
Does not work for me. Clicking "Edit" in the ticket shows the "Edit
Ticket" page where edit every ticket field (title, status, etc.) and
also append a new comment/remark, but there seems t
On 15-3-2014 17:08, j. van den hoff wrote:
Does not work for me. Clicking "Edit" in the ticket shows the "Edit
Ticket" page where edit every ticket field (title, status, etc.) and
also append a new comment/remark, but there seems to be no user
interface for editing previous comments even if I sub
24 matches
Mail list logo
