-scm.org
To: fossil-users@lists.fossil-scm.org
ReplyTo: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] _FOSSIL_ vs. .fos Was: New features for, merging
Sent: 13 Aug 2011 14:39
> Having _different_ defaults complicates both documentation and support, and
> i highly recommend agai
> Having _different_ defaults complicates both documentation and support, and
> i highly recommend against it.
>
I would normally agree, but when the two platforms have different
methods to hide files, I think it's fair to use the native method for
each. I'd support defaulting to .fos or .foss
On Sat, Aug 13, 2011 at 03:46:18PM +0800, Michael Richter wrote:
> On 13 August 2011 07:31, Joerg Sonnenberger wrote:
>
> > (if you can figure out how to mark _FOSSIL_ as hidden on Windows,
> > that would be good too).
> >
>
> The ATTRIB command isn't working for you?
Let me add: "without calli
On Sat, Aug 13, 2011 at 1:29 PM, Remigiusz Modrzejewski
wrote:
> I'd go with .fossil as default on Unix (there is really no good reason to
> limit ourselves to 3 letters here) and hidden _FOSSIL_ on Windows.
>
Having _different_ defaults complicates both documentation and support, and
i highly re
On Aug 13, 2011, at 00:42 , Richard Hipp wrote:
>> Most notably shell's glob ignores dotfiles, what makes them mostly a
>> non-issue for me... And I find the _FOSSIL_ string particularly disturbing
>> on listings.
>>
>
> You know you can rename _FOSSIL_ as .fos, right?
>
> mv _FOSSIL_ .fos
On 13 August 2011 07:31, Joerg Sonnenberger wrote:
> (if you can figure out how to mark _FOSSIL_ as hidden on Windows,
> that would be good too).
>
The ATTRIB command isn't working for you?
--
"Perhaps people don't believe this, but throughout all of the discussions of
entering China our focus
+1
> - Original Message -
> From: Joerg Sonnenberger
> Sent: 08/13/11 05:01 AM
> To: fossil-users@lists.fossil-scm.org
> Subject: Re: [fossil-users] _FOSSIL_ vs. .fos Was: New features for merging
>
> On Fri, Aug 12, 2011 at 06:42:23PM -0400, Richard Hipp wrote:
On Fri, Aug 12, 2011 at 06:42:23PM -0400, Richard Hipp wrote:
> You know you can rename _FOSSIL_ as .fos, right?
>
> mv _FOSSIL_ .fos
>
> Should I make .fos the default?
I think .fos is too random / short. .fossil would be fine as default on
UNIX (if you can figure out how to mark _FOSSIL_
On Fri, Aug 12, 2011 at 3:42 PM, Richard Hipp wrote:
>
>
> On Fri, Aug 12, 2011 at 5:24 PM, Remigiusz Modrzejewski <
> l...@maxnet.org.pl> wrote:
>
>>
>> On Aug 12, 2011, at 22:28 , Ben Summers wrote:
>>
>> >> If it has to be in the file system, I'd prefer one file to many. At the
>> very least,
On Sat, Aug 13, 2011 at 12:42 AM, Richard Hipp wrote:
> You know you can rename _FOSSIL_ as .fos, right?
>
> mv _FOSSIL_ .fos
>
> Should I make .fos the default
>
While i'm all for Unix-style names, i think the name .fos might confuse more
people than it would help, whereas _FOSSIL_ "clearl
On Fri, Aug 12, 2011 at 5:24 PM, Remigiusz Modrzejewski
wrote:
>
> On Aug 12, 2011, at 22:28 , Ben Summers wrote:
>
> >> If it has to be in the file system, I'd prefer one file to many. At the
> very least, change the name of the directory to something that starts with
> __FOSSIL__ to make it eas
11 matches
Mail list logo
