On 05/17/2013 06:10 PM, Eugene Sajine wrote:
> MIchael, sorry for dup - didn't press reply all for the first one.
>
>>
>> So what are you going to do, use cvsimport whenever you cannot *prove*
>> that it is wrong? You sure have low standards for your software.
>
> 1. You are making assumptions a
MIchael, sorry for dup - didn't press reply all for the first one.
>
> So what are you going to do, use cvsimport whenever you cannot *prove*
> that it is wrong? You sure have low standards for your software.
1. You are making assumptions and conclusions that have no grounds.
I asked for help un
On 05/17/2013 03:34 PM, Andreas Krey wrote:
> On Fri, 17 May 2013 15:14:58 +, Michael Haggerty wrote:
> ...
>> We both know that the CVS history omits important data, and that the
>> history is mutable, etc. So there are lots of hypothetical histories
>> that do not contradict CVS. But some t
On Fri, 17 May 2013 15:14:58 +, Michael Haggerty wrote:
...
> We both know that the CVS history omits important data, and that the
> history is mutable, etc. So there are lots of hypothetical histories
> that do not contradict CVS. But some things are recorded unambiguously
> in the CVS histo
On Fri, May 17, 2013 at 9:34 AM, Andreas Krey wrote:
> On Fri, 17 May 2013 15:14:58 +, Michael Haggerty wrote:
> ...
>> We both know that the CVS history omits important data, and that the
>> history is mutable, etc. So there are lots of hypothetical histories
>> that do not contradict CVS.
On 05/17/2013 01:50 PM, Martin Langhoff wrote:
> On Fri, May 17, 2013 at 5:10 AM, Michael Haggerty
> wrote:
>> For one-time imports, the fix is to use a tool that is not broken, like
>> cvs2git.
>
> As one of the earlier maintainers of cvsimport, I do believe that
> cvs2git is less broken, for o
On Fri, May 17, 2013 at 5:10 AM, Michael Haggerty wrote:
> For one-time imports, the fix is to use a tool that is not broken, like
> cvs2git.
As one of the earlier maintainers of cvsimport, I do believe that
cvs2git is less broken, for one-shot imports, than cvsimport. Users
looking for a one-sho
On Fri, May 17, 2013 at 11:10:03AM +0200, Michael Haggerty wrote:
> On 05/15/2013 08:03 PM, Eugene Sajine wrote:
> > My primary goal was to understand better what are the real problems
> > that we might have with the way we use git cvsimport, so I was not
> > asking about the guarantee of the cvsim
On 05/15/2013 08:03 PM, Eugene Sajine wrote:
> My primary goal was to understand better what are the real problems
> that we might have with the way we use git cvsimport, so I was not
> asking about the guarantee of the cvsimport to import things
> correctly, but if there is a guarantee the import
Hi
My primary goal was to understand better what are the real problems
that we might have with the way we use git cvsimport, so I was not
asking about the guarantee of the cvsimport to import things
correctly, but if there is a guarantee the import will result in
completely broken history. IF ther
On 05/15/2013 12:19 AM, Junio C Hamano wrote:
> Eugene Sajine writes:
>
>> What if there are a lot of branches in the CVS repo? Is it guaranteed
>> to be broken after import?
>
> Even though CVS repository can record branches in individual ,v
> files, reconstructing per branch history and where
Eugene Sajine writes:
> What if there are a lot of branches in the CVS repo? Is it guaranteed
> to be broken after import?
Even though CVS repository can record branches in individual ,v
files, reconstructing per branch history and where the branch
happened in each "changeset" cannot be determin
Hi,
We are using git cvsimport heavily but mostly the projects are not
using branches that much. We are also migrating our repos only once,
so there is no commits to CVS repo and no incremental imports allowed
after the migration. we have migrated more than a thousand projects
already.
we use th
13 matches
Mail list logo
