From: lamikr <lamikr@cc.jyu.fi>
To: Shawn Pearce <spearce@spearce.org>
Cc: Jon Smirl <jonsmirl@gmail.com>, Carl Worth <cworth@cworth.org>,
Martin Langhoff <martin.langhoff@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Some tips for doing a CVS importer
Date: Tue, 21 Nov 2006 21:56:18 +0200 [thread overview]
Message-ID: <456359E2.8010403@cc.jyu.fi> (raw)
In-Reply-To: <20061121063934.GA3332@spearce.org>
Shawn Pearce wrote:
> Jon Smirl <jonsmirl@gmail.com> wrote:
>
>> brendan said SVN is likely for the main Mozilla repo and monotone for
>> the new Mozilla 2 work. No native win32 caused git to be immediately
>> discarded.
>>
>
> Yea, that lack of native win32 seems to be one of a number of
> blockers for people switching their projects onto Git.
>
> I think there's a number of issues that are keeping people from
> switching to Git and are instead causing them to choose SVN, hg
> or Monotone:
>
> - No GUI.
>
QGIT allows using some commands. I plan to try out the GIT eclipse
plugin in near future myself.
This mail list have some discussion and download link to it's repo in
archives.
(title: Java GIT/Eclipse GIT version 0.1.1, )
> - No native win32 installation.
> - CVS import fails on some projects (e.g. Mozilla).
>
Well, committing the files from Mozilla cvs to svn has also own problems.
SVN accepts only a text files which have either a "Unix" or DOS style
line endings.
If file contains a both some lines using "Unix" way and others using dos
way SVN roll's
back the commit and you need to tools like "dos2unix" or "unix2dos" to
manipulate those.
(And randomly changing all to either of those is propably not a good idea)
next prev parent reply other threads:[~2006-11-21 19:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 21:49 Some tips for doing a CVS importer Jon Smirl
2006-11-20 23:03 ` Martin Langhoff
2006-11-20 23:37 ` Jon Smirl
2006-11-21 0:29 ` Martin Langhoff
2006-11-21 0:55 ` Carl Worth
2006-11-21 1:40 ` Jon Smirl
2006-11-21 6:39 ` Shawn Pearce
2006-11-21 19:56 ` lamikr [this message]
2006-11-21 20:05 ` Shawn Pearce
2006-11-23 19:45 ` Robin Rosenberg
2006-11-25 6:59 ` Shawn Pearce
2006-11-21 20:03 ` Petr Baudis
2006-11-21 20:15 ` Shawn Pearce
2006-11-21 20:22 ` Johannes Schindelin
2006-11-23 9:10 ` Johannes Sixt
2006-11-21 20:40 ` Martin Langhoff
2006-11-21 1:53 ` Jon Smirl
2006-11-26 10:18 ` Marko Macek
2006-11-26 15:35 ` Jon Smirl
2006-11-26 16:11 ` Marko Macek
2006-11-26 17:51 ` Jon Smirl
2006-11-27 11:29 ` Michael Haggerty
2006-11-21 6:43 ` Shawn Pearce
2006-11-27 11:24 ` Michael Haggerty
2006-11-27 11:51 ` Markus Schiltknecht
2006-11-27 22:09 ` Michael Haggerty
2006-11-28 15:18 ` Markus Schiltknecht
2006-11-30 0:35 ` Michael Haggerty
2006-11-30 0:45 ` Daniel Jacobowitz
2006-11-27 15:20 ` Jon Smirl
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=456359E2.8010403@cc.jyu.fi \
--to=lamikr@cc.jyu.fi \
--cc=cworth@cworth.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=martin.langhoff@gmail.com \
--cc=spearce@spearce.org \
/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).