Fwd: sadly requesting help

Thank you Samuel,

We have plans to migrate to git in the near-ish future.

I'm doing my best to show it's merits to my colleagues.

I'm still a newbie, with only weeks of experience. But already it has
saved many hours of my time and allowed me to work much more
effectively and comfortably. I have at least 5-10 local branches that
I trivially hop across during the course of a day. I would have never
dared to do this with subversion. It was hard to innovate, and since
innovation is my job, git saved my day!

Ray

On Wed, Mar 31, 2010 at 4:53 AM, Samuel Tardieu [off-list ref] wrote:

quoted

quoted

quoted

quoted

quoted

"Raymond" == Raymond Auge [off-list ref] writes:

Raymond> We had a colo failure over the last day or so and lost the last
Raymond> 50-60 commits on our subversion repository (apparently, our
Raymond> backup strategy was not granular enough).

Raymond> Luckily I use Git locally using the git-svn conduit.

Raymond> I need to rewind my repository to an earlier revision and I'm
Raymond> hoping not to have to rebuild my local repo as the project is
Raymond> huge and takes me at least 16 hours to checkout using git-svn.

I know this does not answer your question, but why not use this incident
to switch to git, or at least to seriously investigate a possible future
switch to git?

As you probably know, with git it would have been really easy to restore
the full repository if at least one person does have a local copy of
each branch (typically, the last person to have committed on a branch is
likely to still have a full copy of the branch). And backups can be done
simply by running "git fetch" from a secondary machine at regular
intervals.

Success story: the company I worked for in 2008 had a similar incident a
few months after we switched from svn to git. Not only were we able to
restore a full repository copy, but also we were able to work in the
meantime by setting one of the developers machine as the central
repository, and development work was not disrupted for more than one
hour (we had to educate some developers who were not familiar with
setting remotes other than "origin" and pushing to them). We ran this
degraded setting for a few days (degraded because we lost continuous
testing and packaging capabilities that ran on the main server, and
developers had to run the test themselves by issuing frequent "make
check" commands), but it was certainly not considered a major failure.

In four words: git saved the day.

 Sam
--
Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/

Raymond Augé
Senior Software Architect
Liferay Inc.
--
Liferay East Coast Symposium
Jun 8-9, 2010
Reston, VA
Register today!
--
Follow us on Twitter: liferay