ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <pgesang@ix.urz.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Modules section login (Was: Transliterator module, 2nd revision)
Date: Fri, 12 Mar 2010 10:42:42 +0100	[thread overview]
Message-ID: <20100312094242.GC32282@aides> (raw)
In-Reply-To: <20100311093250.GA28075@aides>


[-- Attachment #1.1: Type: text/plain, Size: 969 bytes --]

Hi again,


On 2010-03-11 <10:32:50>, Philipp Gesang wrote:
> On 2010-03-10 <17:01:46>, Wolfgang Schuster wrote:
> > >I have opened a bitbucket account in order to not to clutter the mailing
> > >list with archives.  The tip revision can be found here:
> > >http://bitbucket.org/phg/transliterator/get/2fc2b5fbbd46.gz
> > >and the precompiled manual over here:
> > >http://bitbucket.org/phg/transliterator/downloads/transliterator.pdf
> > Can you also add the module to the module section [1] on the wiki,
> Humble question: How do I add a module?  The modules login asks for the
> wiki login data, thus I created a wiki account.  But the modules page
> doesn't accept it …

Sorry if this sounds confused.

My wiki account is now almost two days old but I still can't login at
the modules section.  I tried almost all possible permutations of login
name, full name, upper-/lowercase to no avail.  How does it really work?

Regards,


Philipp

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2010-03-12  9:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  9:47 Transliterator module, 2nd revision Philipp Gesang
2010-03-10 16:01 ` Wolfgang Schuster
2010-03-10 22:09   ` Mojca Miklavec
2010-03-11  7:44     ` RCS/git server (was: Transliterator module, 2nd revision) Henning Hraban Ramm
2010-03-11 11:52       ` John Haltiwanger
2010-03-11  8:06     ` Transliterator module, 2nd revision Patrick Gundlach
2010-03-11  9:28       ` VCS for modules (was: Re: Transliterator module, 2nd revision) Peter Münster
2010-03-11  9:31         ` luigi scarso
2010-03-11 11:12         ` Mojca Miklavec
2010-03-11 12:03           ` VCS for modules Hans Hagen
2010-03-11 11:25       ` Transliterator module, 2nd revision Mojca Miklavec
2010-03-11  9:32   ` Philipp Gesang
2010-03-11  9:58     ` Jelle Huisman
2010-03-11 10:33       ` Hans Hagen
2010-03-12  9:42     ` Philipp Gesang [this message]
2010-03-12  9:57       ` Modules section login (Was: Transliterator module, 2nd revision) Patrick Gundlach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100312094242.GC32282@aides \
    --to=pgesang@ix.urz.uni-heidelberg.de \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).