Re: import determinism

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

 



* Andreas Schwab <schwab@xxxxxxxxxxxxxx> wrote:

> > For cvsimport, it is not deterministic. Given cvs'
> > ambiguous/buggy/inconsistent internal semantics around some
> > operations, cvsps makes educated guesses about what happened.
> >
> > Later commits can affect those educated guesses.
> 
> The OP was assuming an unchanging repository.

My assumption is:

* the original cvs repo will have later additions
  (so I'm incrementally importing)
* no commints (besides cvsimport) in the git mirror, but others
  for off from there
* the mirror could get lost in an desaster (no separate backup)
  and should be recreated afresh in that case.


The point behind this is: I'm running a growing number of cvs2git
mirrors and dont want to do full backups of them.


cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt@xxxxxxxx
 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
--
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]