ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: git or svn
Date: Fri, 27 Sep 2013 16:27:23 +0200	[thread overview]
Message-ID: <524595CB.7000204@wxs.nl> (raw)
In-Reply-To: <20130927152625.12c967ca@aga-netbook>

On 9/27/2013 3:26 PM, Marcin Borkowski wrote:

> Also, if this matters, Git has an excellent Emacs front-end, Magit.  I
> don't know whether SVN has something similar.

github has a nice windows backend but (as with more open source 
developments) the real nice stuff is closed ... i tried several times 
but never could install easily some git server infrastructure similar to 
github on a (linux) server so at our company we stay with svn (but i 
keep copies of the context-on-github on my machine, but only for viewing)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2013-09-27 14:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 19:53 ConTeXt Manual Errata 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
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 [this message]
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=524595CB.7000204@wxs.nl \
    --to=pragma@wxs.nl \
    --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).