From: Martin Langhoff <martin.langhoff@gmail.com>
To: "weigelt@metux.de" <weigelt@metux.de>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: import determinism
Date: Tue, 9 Nov 2010 23:40:52 -0500 [thread overview]
Message-ID: <AANLkTi=y_DKRRU43ro3WDz2rSDGL9xASfsinoj8Ya9PT@mail.gmail.com> (raw)
In-Reply-To: <20101109134337.GA19430@nibiru.local>
Every full clone is a good backup. If nobody is doing a full clone...
the do back them up. That's my recommendation.
M
On Tuesday, November 9, 2010, Enrico Weigelt <weigelt@metux.de> wrote:
> * Andreas Schwab <schwab@linux-m68k.org> 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@metux.de
> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2010-11-10 4:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 20:25 import determinism Enrico Weigelt
2010-11-07 20:46 ` Ævar Arnfjörð Bjarmason
2010-11-07 21:01 ` Andreas Schwab
2010-11-07 21:56 ` Enrico Weigelt
2010-11-07 22:20 ` Martin Langhoff
2010-11-07 22:45 ` Andreas Schwab
2010-11-09 13:43 ` Enrico Weigelt
2010-11-10 4:40 ` Martin Langhoff [this message]
2010-11-10 16:18 ` Enrico Weigelt
2010-11-10 21:25 ` Martin Langhoff
2010-11-10 22:04 ` Enrico Weigelt
2010-11-11 4:28 ` Michael Haggerty
2010-11-11 13:09 ` Enrico Weigelt
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='AANLkTi=y_DKRRU43ro3WDz2rSDGL9xASfsinoj8Ya9PT@mail.gmail.com' \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=weigelt@metux.de \
/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).