On Sat, Jan 17, 2009 at 08:55:50PM +0600, Anatoly A. Kazantsev wrote:
> Hello!
>
> There's no option to enable Mercurial in GNU Russian Translation Team.
> Group type is 'www.gnu.org translation team'
This is fixed.
Thanks for the report.
--
Sylvain
Hello!
There's no option to enable Mercurial in GNU Russian Translation Team.
Group type is 'www.gnu.org translation team'
--
Anatoly A. Kazantsev
Protect your digital freedom and privacy, eliminate DRM, learn more at
http://www.defectivebydesign.org/what_is_drm
pgpart3yMqHAd.pgp
Description:
Update of sr #106603 (project administration):
Status:None => Done
Assigned to:None => Beuc
Open/Closed:Open => Closed
__
Update of sr #106037 (project administration):
Status:None => Done
Open/Closed:Open => Closed
___
Follow-up Comment #4:
Thanks for
Follow-up Comment #34, sr #106304 (project administration):
>From what I remember it was registered 12th january, so it did pass the
TextCHA.
My understanding of the stats is that spammers combine initial manual setup
with later automated spamming. In this case I presume the spammer's cronjob
re
> > and added them to the aliases on monty python. Now, the downside of this
> > is that you can no longer add entries to this file. If you want to be
> > able to edit it, we could set up a cron job that rsyncs it off a place
> > on savannah somewhere, if you like.
>
> That would be nice, yes.
> H
> > and added them to the aliases on monty python. Now, the downside of this
> > is that you can no longer add entries to this file. If you want to be
> > able to edit it, we could set up a cron job that rsyncs it off a place
> > on savannah somewhere, if you like.
>
> That would be nice, yes.
> H
