From: "René Moser" <mail@renemoser.net>
To: git@vger.kernel.org
Subject: cvs update vs. git pull
Date: Fri, 28 May 2010 11:21:12 +0200 (CEST) [thread overview]
Message-ID: <d876ae6b75ab8d9debe5b97f84a4386a.squirrel@resmo.ch> (raw)
Hi
I use git since a while for my own projects (how surprise).
The company I work for still uses a CVS(nt), and this sucks, time to
changed that. We have a use case we often have problems with. If git would
solve this problem, I would really have a good arg for the managers.
The codebase managed by CVS is quite huge and therefore we have daily and
nightly builds.
One problem we have is, that if there is a commit to cvs while the cvs
update of the build job is running (and this takes 20 minutes), then we
get some inconsistence, the build will fail.
So the question is, if we would use git, this inconsistence would not be
possible because the git pull will get the state of the sha1. Right?
Thanks in advance for your clearification.
Regards
René
next reply other threads:[~2010-05-28 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 9:21 René Moser [this message]
2010-05-28 9:35 ` cvs update vs. git pull Andreas Ericsson
2010-05-28 9:46 ` Tor Arntsen
2010-05-28 9:54 ` Matthieu Moy
2010-05-28 13:07 ` Ævar Arnfjörð Bjarmason
2010-05-28 15:58 ` Robin Rosenberg
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=d876ae6b75ab8d9debe5b97f84a4386a.squirrel@resmo.ch \
--to=mail@renemoser.net \
--cc=git@vger.kernel.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).