Michai Ramakers wrote:
>
> I was unclear; this is the corresponding timeline:
>
> === 2015-07-29 ===
> 19:58:39 [70b61c707b] *CURRENT* x (user: michai tags: trunk)
>DELETED d/dd/f
>DELETED d/f
>ADDED e/dd/f
>ADDED e/f
> 19:57:26 [998d26af68] a (user: michai tags: trunk)
>ADDED
On 29 July 2015 at 22:02, Michai Ramakers wrote:
> On 29 July 2015 at 21:29, Joe Mistachkin wrote:
>>
>> Michai Ramakers wrote:
>>>
>>> Right... creating the target-dir 'd2' beforehand worked in my case;
>>> any subdir existing under 'd' seems to be moved under 'd2' afterwards.
>>>
>>
>> I think
On 29 July 2015 at 22:02, Michai Ramakers wrote:
>
> (the corresponding timeline shows 2 added and 2 deleted files, and
> history is lost)
I mean of course: there is no relation between the added and deleted
files, history-wise.
Michai
___
fossil-users
On 29 July 2015 at 21:29, Joe Mistachkin wrote:
>
> Michai Ramakers wrote:
>>
>> Right... creating the target-dir 'd2' beforehand worked in my case;
>> any subdir existing under 'd' seems to be moved under 'd2' afterwards.
>>
>
> I think the following change will fix the issue:
>
> https:/
Michai Ramakers wrote:
>
> Right... creating the target-dir 'd2' beforehand worked in my case;
> any subdir existing under 'd' seems to be moved under 'd2' afterwards.
>
I think the following change will fix the issue:
https://www.fossil-scm.org/fossil/info/b86127e187a00bfc
--
Joe Mista
On Wed, Jul 29, 2015 at 7:22 PM, Paul Pereira wrote:
> The path /var/www is the chroot folder. It is not publicly visible by
>
Ah, right - chroot. i run on a cheap shared hoster where chroot isn't an
option, so i've never used that feature :/.
> I would add
> - Fossil must be able to create te
Hi Stephan,
On Wed, Jul 29, 2015 at 5:28 PM, Paul Pereira wrote:
> It's not common practice (for me, at least) to put the repo file in a path
> reachable by www clients. On my hoster all of my CGI-hosted repos live in
> some dir under my home dir, writable by my account, the CGI scripts all
> po
Thus said "Joe Mistachkin" on Tue, 28 Jul 2015 21:02:49 -0700:
> It might be nice to have test coverage for the new command.
Yes, very good point. I'll add some later today (time permitting).
Thanks,
Andy
--
TAI64 timestamp: 400055b90a22
___
fossi
On 29 July 2015 at 16:50, Michai Ramakers wrote:
> Hello,
>
> using 'fossil mv' for the first time, and for some reason I don't
> understand what happens here (see pasted output) - instead of renaming
> a dir, it creates a zero-byte file (and leaves the original dir
> as-is).
>
> I have the feelin
On Wed, Jul 29, 2015 at 5:28 PM, Paul Pereira wrote:
> It may be worth mentioning in the CGI setup instructions that
> Fossil/sqlite needs to be able to create temporary files for rollback logs
> in some manner particular to the OS, such as by writing to /tmp.
>
> In my case, I installed Fossil a
It may be worth mentioning in the CGI setup instructions that Fossil/sqlite
needs to be able to create temporary files for rollback logs in some manner
particular to the OS, such as by writing to /tmp.
In my case, I installed Fossil according to the standard chroot procedure
in OpenBSD for CGI app
On 7/29/15, Sean Woods wrote:
> If I use the URL /artifact/ I am taken to a source code
> listing of .
>
> How can I do the same by filename? Suppose I want the HEAD version of a
> given file, and I always want that URL to point to the HEAD version?
>
> Also (if not too much trouble) -- if someon
Hello,
using 'fossil mv' for the first time, and for some reason I don't
understand what happens here (see pasted output) - instead of renaming
a dir, it creates a zero-byte file (and leaves the original dir
as-is).
I have the feeling I'm doing something really simple really wrong. Ideas..?
Mich
If I use the URL /artifact/ I am taken to a source code
listing of .
How can I do the same by filename? Suppose I want the HEAD version of a
given file, and I always want that URL to point to the HEAD version?
Also (if not too much trouble) -- if someone could point me to the code
where this is
On Wed, Jul 29, 2015 at 6:34 AM, Steve Stefanovich wrote:
>> From: Paolo Bolzoni
>> Sent: Wednesday, 29 July 2015 08:38
>> fossil commit "filename"
>> might help you in your problem?
> It gets messy when there is a number of files, on Windows at least where
> using pipes and xargs is limited co
I would appreciate if anyone on the list can clarify if the following is a bug
or expected behaviour. I hope the diagrams will come out OK when this is posted.
I'm developing some features in 'x' branch, with a plan to merge periodically
in another branch 'y', when stable. So I have added some f
16 matches
Mail list logo
