On Saturday 16 July 2005 20:36, Paweł Sakowski wrote:
> On Sat, 2005-07-16 at 17:02 +0300, Elan Ruusamäe wrote:
> > i was more thinking why NAME.cron not NAME-cron.
>
> Hmm... probably because it's more natural -- the nomenclature
> name.extension (a.k.a. contents_description.type) has been around
On Sat, 2005-07-16 at 17:02 +0300, Elan Ruusamäe wrote:
> i was more thinking why NAME.cron not NAME-cron.
Hmm... probably because it's more natural -- the nomenclature
name.extension (a.k.a. contents_description.type) has been around for
years. OTOH: any reasons to start using NAME-cron?
--
Paw
On Saturday 16 July 2005 15:36, Paweł Sakowski wrote:
> glen committed:
> > Naming files in SOURCES.
> > few unexplained conventions (if smb knows, plz explain the reasons):
> > - NAME-foo.patch - patches
> > - NAME.cron - cron fragments which go to /etc/cron.d dir
> > - NAME.logrotate - logrotate
glen committed:
> Naming files in SOURCES.
> few unexplained conventions (if smb knows, plz explain the reasons):
> - NAME-foo.patch - patches
> - NAME.cron - cron fragments which go to /etc/cron.d dir
> - NAME.logrotate - logrotate config whichgoes to /etc/logrotate.d
> - NAME.sysconfig - applicat
