Nicola Ken Barozzi wrote:
Ferdinand Soethe wrote:
...
Believe me, as I have already suffered consequences from my bad habit of
sending quick mails ;-)
Absolutely, we have all been there (and I still go there unfortunately).
One of my blog entries describes how I *try* and manage the horrible
flou
Ferdinand Soethe wrote:
...
My problem is not different threads but the temptation of sending instant
replies. I just needed to take the time, read all new stuff and then
respond to avoid this.
Instant replies also tend to lower the signal2noise ratio, can create
tensions in case of important disc
In 'Re: Comment on index.html (Re: Where to change comments to
configuration files)'
Ross Gardler wrote:
FS> Sorry, I shouldn't respond to messages one by one. That way I missed
FS> your solution in 'Re: Inkonsistency in implementation of default file
FS> and sit
Ferdinand Soethe wrote:
Ross Gardler wrote:
RG> But that simply is not correct. It *is* configurable as I have written
RG> on a number of occasions now.
Sorry, I shouldn't respond to messages one by one. That way I missed
your solution in 'Re: Inkonsistency in implementation of default file
and sit
On Tue, 2005-05-03 at 09:49 +0100, Ross Gardler wrote:
> Ferdinand Soethe wrote:
> >...
> > I disagree here. It might have been ok to just leave it before we knew
> > about the inconsistencies it will create if you don't use index.html.
>
> As far as I am aware the only inconsistency is that the i
Ross Gardler wrote:
RG> But that simply is not correct. It *is* configurable as I have written
RG> on a number of occasions now.
Sorry, I shouldn't respond to messages one by one. That way I missed
your solution in 'Re: Inkonsistency in implementation of default file
and site.xml and what to do
Ferdinand Soethe wrote:
Ross Gardler wrote:
(about this comment
FS> >
)
RG> I'm -1 on the current comment as it gives the impression that it *can't*
RG> be changed. This is bad. If someone needs to change it and they read
RG> that comment then they will not bother to search the docs/ask on the
RG>
Ross Gardler wrote:
(about this comment
FS> >
)
RG> I'm -1 on the current comment as it gives the impression that it *can't*
RG> be changed. This is bad. If someone needs to change it and they read
RG> that comment then they will not bother to search the docs/ask on the
RG> mailing lists.
R
Ferdinand Soethe wrote:
Ross Gardler wrote:
RG> Best to change it in all occurances of the file as people could look at
RG> any of the official Apache docs for guidance.
Added info to files in fresh-site and site author. I'd rather not
do this in the future but instead prefer for us to agree that w
Ross Gardler wrote:
RG> Best to change it in all occurances of the file as people could look at
RG> any of the official Apache docs for guidance.
Added info to files in fresh-site and site author. I'd rather not
do this in the future but instead prefer for us to agree that we will
maintain the '
Ferdinand Soethe wrote:
copied from the user list
I'll add a comment about this in site.xml
>
is it correct to change the files in fresh site if I wanted to add
comments to skinconf.xml or do I need to change that file somewhere
else?
Best to change it in all occurances of the file as people could
11 matches
Mail list logo