ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mica Semrick <paperdigits@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt Manual Errata
Date: Thu, 26 Sep 2013 14:22:07 -0700	[thread overview]
Message-ID: <CABkompJyXE-HW5fmpU2eHKQwf2Uac9m8ZXLNZ3FfBCptimcmOg@mail.gmail.com> (raw)
In-Reply-To: <87ob7f1fir.fsf@micropit.couberia.selfip.net>


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

@Peter github makes collaboration quite painless. Users can manage their
own accounts.

+1 for github from me too!


On Thu, Sep 26, 2013 at 1:42 PM, Peter Münster <pmlists@free.fr> wrote:

> On Thu, Sep 26 2013, Aditya Mahajan wrote:
>
> > Wouldn't it be better to move the manuals to github rather than keeping
> them
> > on an svn server?
>
> Why?
>
> --
>            Peter
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 1744 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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
___________________________________________________________________________________

  reply	other threads:[~2013-09-26 21:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 19:53 Thangalin
2013-09-21 17:15 ` Marco Patzer
2013-09-26 17:44   ` Marco Patzer
2013-09-26 20:07     ` Thangalin
2013-09-26 20:15       ` Aditya Mahajan
2013-09-26 20:31         ` Marco Patzer
2013-09-26 20:42         ` Peter Münster
2013-09-26 21:22           ` Mica Semrick [this message]
2013-09-26 21:50             ` git or svn (was: ConTeXt Manual Errata) Peter Münster
2013-09-26 21:56               ` Mica Semrick
2013-09-26 23:24                 ` Thangalin
2013-09-27  6:46                 ` git or svn Peter Münster
2013-09-27  1:10               ` git or svn (was: ConTeXt Manual Errata) Aditya Mahajan
2013-09-27  7:01                 ` git or svn Peter Münster
2013-09-27  7:38                   ` Taco Hoekwater
2013-09-27 13:01                     ` Lars Huttar
2013-09-27 13:10                 ` Lars Huttar
2013-09-27 13:26                   ` Marcin Borkowski
2013-09-27 14:02                     ` Peter Münster
2013-09-27 14:27                     ` Hans Hagen
2013-09-27 17:08                       ` Mica Semrick
2013-09-26 23:22             ` ConTeXt Manual Errata Thangalin
2013-09-27  9:10           ` Marco Patzer
2013-09-27  9:27             ` Peter Münster
2013-09-26 20:17       ` Marco Patzer

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=CABkompJyXE-HW5fmpU2eHKQwf2Uac9m8ZXLNZ3FfBCptimcmOg@mail.gmail.com \
    --to=paperdigits@gmail.com \
    --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).