[277404] in TECHWR-L
[TECHWR-L] - What are your experiences with version control system
daemon@ATHENA.MIT.EDU (sereshk 146)
Mon Dec 1 18:48:04 2025
Date: Mon, 1 Dec 2025 15:42:41 -0800 (PST)
From: sereshk 146 <sereshk146@gmail.com>
To: TECHWR-L Email Discussion group <techwr-l@techwr-l.com>
Message-Id: <731fdd1e-9af5-45e0-b5f6-f0b78b590df5n@techwr-l.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_1682294_581211953.1764632561629"
Reply-To: techwr-l@techwr-l.com
------=_Part_1682294_581211953.1764632561629
Content-Type: multipart/alternative;
boundary="----=_Part_1682295_1626416131.1764632561629"
------=_Part_1682295_1626416131.1764632561629
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hello Everyone,
I've been using version control in several teams and have got some=20
experience already, mainly git and SVN + TortoiseSVN.=20
Setting up a good file and folder structure and make everyone aware of=20
how-tos is an important starting point, to my mind...
We are looking at ways and procedures in our small team to best handle=20
daily collaboration using SVN on software product and feature=20
documentation, including XML-based CCMS.
Especially the merging of conflicts is a rather-to-be-avoided issue. :) As=
=20
far as possible.
I would like to read about your views and tips or learnings you might want=
=20
to share here very much, in order to make our current restructuring and=20
planning process a success.
Thanks in advance! Looking forward to any contributions! Highly appreciated=
!
Kind Regards
Nina
--=20
TechWR-L is the =E2=80=9CTechnical Writers List=E2=80=9D =E2=80=94 an email=
discussion list focused on all issues in technical communicatio
---=20
You received this message because you are subscribed to the Google Groups "=
TECHWR-L Email Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to techwr-l+unsubscribe@techwr-l.com.
To view this discussion visit https://groups.google.com/a/techwr-l.com/d/ms=
gid/techwr-l/731fdd1e-9af5-45e0-b5f6-f0b78b590df5n%40techwr-l.com.
------=_Part_1682295_1626416131.1764632561629
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div>Hello Everyone,</div><div><br /></div><div>I've been using version con=
trol in several teams and have got some experience already, mainly git and =
SVN + TortoiseSVN.=C2=A0<br />Setting up a good file and folder structure a=
nd make everyone aware of how-tos is an important starting point, to my min=
d...</div><div><br /></div><div>We are looking at ways and procedures in ou=
r small team to best handle daily collaboration using SVN on software produ=
ct and feature documentation, including XML-based CCMS.<br /><br /></div><d=
iv>Especially the merging of conflicts is a rather-to-be-avoided issue. :) =
As far as possible.</div><div><br /></div><div>I would like to read about y=
our views and tips or learnings you might want to share here very much, in =
order to make our current restructuring and planning process a success.</di=
v><div><br /></div><div>Thanks in advance! Looking forward to any contribut=
ions! Highly appreciated!</div><div><br /></div><div>Kind Regards</div><div=
>Nina</div>
<p></p>
-- <br />
TechWR-L is the =E2=80=9CTechnical Writers List=E2=80=9D =E2=80=94 an email=
discussion list focused on all issues in technical communicatio<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;TECHWR-L Email Discussion group" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:techwr-l+unsubscribe@techwr-l.com">techwr-l+unsub=
scribe@techwr-l.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/a/techwr=
-l.com/d/msgid/techwr-l/731fdd1e-9af5-45e0-b5f6-f0b78b590df5n%40techwr-l.co=
m?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/a/techw=
r-l.com/d/msgid/techwr-l/731fdd1e-9af5-45e0-b5f6-f0b78b590df5n%40techwr-l.c=
om</a>.<br />
------=_Part_1682295_1626416131.1764632561629--
------=_Part_1682294_581211953.1764632561629--
