2012/6/13 Rene :
> On 2012-06-12 00:36, Mike Meyer wrote:
>>
>> My boss just sent me mail that said, and I quote:
>>
>> Fossil sucks and is actually not compatible with Windows
>>
>
> Mike,
>
> ...
> Better sit down with him and ask him what the problem is, maybe first a few
> pints of strong lag
On 2012-06-12 00:36, Mike Meyer wrote:
My boss just sent me mail that said, and I quote:
Fossil sucks and is actually not compatible with Windows
I'm pretty sure I've seen people here who use it no Windows, and
there's a Windows distribution, which makes me think he's wrong.
His problem is
On Tue, Jun 12, 2012 at 9:15 PM, Mike Meyer wrote:
> We're not talking about a repository that's being served by an HTTP
> server, but about the repository that's on his machine.
>
>> However... once a developer clones the repo, if he has it on a public
>> filesystem then all bets are off.
>
> Exa
On Wed, Jun 13, 2012 at 3:15 AM, Mike Meyer wrote:
> Exactly. He wants it on a file system that he's where he's using ACLs
> to control access to the contents of the file system, and fossil is
> apparently refusing to work unless he opens access to those files up
> to everyone. That's not accepta
On Tue, Jun 12, 2012 at 8:48 PM, Stephan Beal wrote:
> On Tue, Jun 12, 2012 at 11:18 PM, Mike Meyer wrote:
>>
>> ACLs. Apparently, using it means that you have to open the sources up
>> to readable by everything/everyone or some such. That's caused him to
>> ask me to install mercurial.
>
>
> Tha
On Tue, Jun 12, 2012 at 11:18 PM, Mike Meyer wrote:
> ACLs. Apparently, using it means that you have to open the sources up
> to readable by everything/everyone or some such. That's caused him to
> ask me to install mercurial.
>
That's a partial misunderstanding: the sources are safely tucked aw
We use fossil on Windows for several ongoing customer projects and are
quite pleased. Out of long-standing habits born of too many years
dealing with command-line tools, we are fairly careful to keep spaces
out of path and file names inside repositories. However, I have several
cases where the
On Tue, Jun 12, 2012 at 5:18 PM, Mike Meyer wrote:
> The other issue is that fossil doesn't pay attention to Windows
> ACLs.
I'm somewhat familiar with Windows ACLs but I don't really know what this
means. Can you be more specific? Usually, file inherit permissions from
their folder. No, fossil
On Tue, 12 Jun 2012 14:45:37 -0400
Ron Wilson wrote:
> In particular, file/directory names with spaces in them need to be
> quoted.
The other issue is that fossil doesn't pay attention to Windows
ACLs. Apparently, using it means that you have to open the sources up
to readable by everything/every
I've only ever used Trac for Issue Tracking and Wiki. Looking at the
documentaiton on the Trac website, it looks like working copy
operations (commit, update, etc.) are done through an "ordinary" SVN
client. Maybe I am missing something, but (in 5 minutes) I could not
find anything about commiting
Hi Mike,
See the sample session below. All works as you would expect.
Obviously, it is a trivial example and I don't mean there are no bugs
in fossil. It's just I've never encountered any w.r.t. spaces in
file/dir names.
Cheers,
Jacek
d:\tmp\space dir>fossil init "d:\cala\data\fossil test
On Tue, 12 Jun 2012 00:15:08 +0100
Jacek Cała wrote:
> Hi,
>
> Could you please be a bit more specific about what errors exactly you
> have experienced.
I wish I could. It's my boss that's having problems, and I've already
sent the full report to him. I'm now pursuing this on my own time.
> I'
On Mon, Jun 11, 2012 at 7:53 PM, Jacek Cała wrote:
> However, I think you usually don't need to specify file names by hand.
> It's enough to issue
> 'fossil add *' or 'fossil add a_dir' or 'fossil add "a_dir\b dir"' and
> fossil will do the job you.
I've used fossil lightly on Windows XP and 7
Hi again,
Sorry for not answering your question in my previous post... I'm a bit
sleepy (it's about 1am my time).
Try double quotes. Just tested with no errors:
> fossil add "new file.txt"
ADDED new file.txt
> fossil chan
ADDED new file.txt
> fossil commit -m "new file added..."
New_Vers
Hi,
Could you please be a bit more specific about what errors exactly you
have experienced.
I've been using fossil on Windows (Vista 32-bit and 7 64-bit) for more
than 3 years now and haven't ever experienced any problems with spaces
in dirs or file names;
Below is an excerpt from the listing of
On Mon, Jun 11, 2012 at 6:36 PM, Mike Meyer wrote:
> My boss just sent me mail that said, and I quote:
>
> Fossil sucks and is actually not compatible with Windows
>
> I'm pretty sure I've seen people here who use it no Windows, and
> there's a Windows distribution, which makes me think he's wr
> -Original Message-
> From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-
> boun...@lists.fossil-scm.org] On Behalf Of Mike Meyer
>
> My boss just sent me mail that said, and I quote:
>
>Fossil sucks and is actually not compatible with Windows
>
> I'm pretty sure I
My boss just sent me mail that said, and I quote:
Fossil sucks and is actually not compatible with Windows
I'm pretty sure I've seen people here who use it no Windows, and
there's a Windows distribution, which makes me think he's wrong.
His problem is that he has lots of spaces in his directo
18 matches
Mail list logo
