From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: git or svn (was: ConTeXt Manual Errata)
Date: Thu, 26 Sep 2013 21:10:48 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1309262105180.30753@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <87k3i31cda.fsf_-_@micropit.couberia.selfip.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1122 bytes --]
On Thu, 26 Sep 2013, Peter Münster wrote:
> On Thu, Sep 26 2013, Mica Semrick wrote:
>
>> @Peter github makes collaboration quite painless. Users can manage their own
>> accounts.
>
> I like git because of its features. And when I don't need those
> features, I prefer svn because of its simplicity. Where is the pain?
The last time I tried, merging multiple version in svn is a huge pain. One
of the advantages of DVCS is that branching and merging are easy.
> What would be the benefit when moving to github?
Github seems to be the most popular DVCS hosting site at the moment. For
manuals, I think that Github is particularly useful because you can click
on edit and make the change. Github automatically creates a fork, a new
branch, and pull request for you. So the technical barrier to
participation is low.
> -1 (not worth the trouble for me)
>
> (On the other hand, if you sent me some bitcoins, I would be glad to
> copy contextman to github. ;)
https://github.com/nirvdrum/svn2git
Using this is usually as simple as
svn2git http://svn.example.com/path/to/repo
Aditya
[-- 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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-09-27 1:10 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 ` Aditya Mahajan [this message]
2013-09-27 7:01 ` 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=alpine.LNX.2.02.1309262105180.30753@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).