I thought about VMS as well, but the [] is just specifying
subdirectories. I think any code to port fossil to VMS should do the
translation from [.SRC.MYAPP.DB]CONNECT.C and store the path as
./src/myapp/db/connect.c. Then the file will checkout on any platform.
As for filenames, that's a li
On Mon, Aug 17, 2009 at 3:35 PM, Stephan Beal wrote:
> On Mon, Aug 17, 2009 at 3:12 PM, Mark Janssen wrote:
>>
>> Hmmm for [] VMS comes to mind.
>> So fossil takes the common denominator for file names on all
>> platforms?
>
> It sounds that way.
>
>>
>> Although that's certainly good for portabil
On Mon, Aug 17, 2009 at 3:12 PM, Mark Janssen wrote:
> Hmmm for [] VMS comes to mind.
> So fossil takes the common denominator for file names on all
> platforms?
It sounds that way.
> Although that's certainly good for portability of the
> repos, it does limit the artifact names you can use.
On Mon, Aug 17, 2009 at 3:08 PM, Stephan Beal wrote:
> On Mon, Aug 17, 2009 at 12:06 PM, Mark Janssen
> wrote:
>>
>> I noticed fossil will not add files containing any of the characters
>> "\*[]?". If I remove the checks for these chars, I cannot find any
>> adverse effects. Is there a specific re
On Mon, Aug 17, 2009 at 12:06 PM, Mark Janssen wrote:
> I noticed fossil will not add files containing any of the characters
> "\*[]?". If I remove the checks for these chars, I cannot find any
> adverse effects. Is there a specific reason these characters are
> forbidden?
>
The "?:*" characters
Hi,
I noticed fossil will not add files containing any of the characters
"\*[]?". If I remove the checks for these chars, I cannot find any
adverse effects. Is there a specific reason these characters are
forbidden?
Regards,
Mark
___
fossil-users mailin
6 matches
Mail list logo
