Re: git-cvsimport - losing changes in subsequent pulls of a CVS branch that I thought I wasn't modifying in the GIT repo.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Michael Haggerty:
> cvs2svn/cvs2git does not support this (called "incremental imports").

git-cvsimport tries to.

> It is quite hard to implement robustly.  In fact, I claim that no tool
> handles incremental imports robustly, despite the fact that some claim
> to do so :-)
> 
As people are habitually mucking with their CVS repositories, your best
way to reliably do an incremental import is to do a regular import,
put the two trees into the same git repository (easily achieved by a
line in .git/objects/info/alternates and strategic copying of the
tip-of-tree references), and git-rebase your non-CVS work.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@xxxxxxxxxxxxxx
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
When mutilating cattle, avoid the ones with testicles.
		-- The Evil Cultist List
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux