From: Andreas Ericsson <ae@op5.se>
To: "René Moser" <mail@renemoser.net>
Cc: git@vger.kernel.org
Subject: Re: cvs update vs. git pull
Date: Fri, 28 May 2010 11:35:18 +0200 [thread overview]
Message-ID: <4BFF8E56.7050805@op5.se> (raw)
In-Reply-To: <d876ae6b75ab8d9debe5b97f84a4386a.squirrel@resmo.ch>
On 05/28/2010 11:21 AM, René Moser wrote:
> 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?
>
Right.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2010-05-28 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 9:21 cvs update vs. git pull René Moser
2010-05-28 9:35 ` Andreas Ericsson [this message]
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=4BFF8E56.7050805@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=mail@renemoser.net \
/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).