From: Lars Huttar <lars_huttar@sil.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: git or svn
Date: Fri, 27 Sep 2013 09:01:10 -0400 [thread overview]
Message-ID: <52458196.9030200@sil.org> (raw)
In-Reply-To: <4B6C1BAC-34E3-4ACC-83DC-86AEC65878E5@elvenkind.com>
On 9/27/2013 3:38 AM, Taco Hoekwater wrote:
> On Sep 27, 2013, at 9:01 AM, Peter Münster <pmlists@free.fr> wrote:
>
>> On Fri, Sep 27 2013, Aditya Mahajan wrote:
>>
>>> 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.
>> I understand. Please go ahead if you need git. My preference for svn is
>> just my personal opinion, coming from my personal experience: people
>> wanted to change a well running system, using the latest and greatest
>> tools. In the end, after quite some efforts, there was no benefit, it
>> was just a bit more complicated.
> +1 from me: I have exactly the same experience personally.
>
I'm with Taco and Peter on this one. SVN is part of my everyday
workflow; Git requires a lot more reading and fumbling. However I know
the need to be fluent with Git is becoming more and more prevalent, and
for many people it's already the easiest thing. So I wouldn't argue
against moving to Git. I'm just reporting my preference.
BTW I committed several changes to the manual yesterday, and plan to do
a fair bit more in the coming week or two. I would appreciate if someone
knowledgeable could check and make sure that I haven't said things that
are misleading or incorrect.
Lars
___________________________________________________________________________________
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 13:01 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 [this message]
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=52458196.9030200@sil.org \
--to=lars_huttar@sil.org \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.com \
/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).