similar to: SVN vs DVCS

Hi, I have been looking at mirroring the SVN R repository into a DVCS (Mercurial, Git, bzr, etc...). The idea would be to have that as an always up-to-date untouched master (a mirror) but having it in a DVCS would make forks easier to make and maintain, and possibly ease up the process of having patches included upstream. Would anyone else be interested ? Laurent

Recently, I've been working on tools for doing high-quality conversions of project histories from centralized version-control systems like Subversion to modern decentralized systems like git and hg. To see what I mean by "high quality", take a look at my DVCS migration guide: <http://www.catb.org/esr/dvcs-migration-guide.html>. A really good conversion should, for example,

Chris Lattner <clattner at apple.com> writes: > I completely agree. The "branch" I most care about is mainline, and > losing the ability to say "fixed in r1234" (with some sort of > monotonically increasing number) would be a tragic loss. The monotonically increasing number is useful for giving you a fuzzy idea about how that change relates to other changes

Joerg Sonnenberger <joerg at britannica.bec.de> writes: > The core issue here is that you are effectively telling us > that the current workflow is not supported by Git. No, it's fully supported. We can even run things exactly the same way. But we don't _have_ to do that. > You are also telling us that the current workflow is in some way wrong > or misguided or

On Jul 22, 2011, at 2:02 PM, Andrew Trick wrote: >> Of course, if you've used SVN extensively, you've been trained to think >> that history has to be somewhat linear, and perhaps even that the trunk >> branch is the only one needing QA attention. Migration from SVN to Git >> is hard because you have to change the mental model, not just command >> names and

Hi, Quite a few people have asked to be able to access OpenSSH sources using a DVCS, so I have made a Mercurial repository available at http://hg.mindrot.org/openssh You can fetch a copy using: hg clone http://hg.mindrot.org/openssh openssh You can also view the web interface directly, which might be handy for fetching diffs of changesets to cherry-pick. The repository is synchronised

On Jul 22, 2011, at 10:55 PM, David A. Greene wrote: >> >> What are the precise gains from changing the status quo? What can you >> do by moving everything to Git that you couldn't do in the current >> world with svn as master repository and the additional git mirror? > > I work on a third-party branch. I can sync with upstream and push our > changes back

Chris Lattner <clattner at apple.com> writes: > I really do appreciate distributed VCS, but only as staging. > Incremental development is crucial for the project and "take this git > push with 100K of code" will never be acceptable. Incremental development is probably promoted by DVCS far more than others. Your comment seems to imply that only the tip of each push is

On Sat, Jul 23, 2011 at 01:02:10AM +0200, Óscar Fuentes wrote: > One thing that I wanted to see (and probably missed, because I didn't > read all the thread) is to discuss the workflow. I'm under the > impression that not all regular LLVM developers understand the > implications for the LLVM community of migrating from a central VCS to a > distributed one, on terms of

Jason Kim <jasonwkim at google.com> writes: > On Wed, Jul 27, 2011 at 8:59 PM, Mark Lacey <641 at rudkx.com> wrote: > > Besides, the git-svn readonly bridge is a great solution for those who want to use git > >   It seems to be a reasonable solution for those individuals who > want to use git, but in my experience not for organizations that >

On Wed, Jul 27, 2011 at 8:59 PM, Mark Lacey <641 at rudkx.com> wrote: > >> Besides, the git-svn readonly bridge is a great solution for those who >> want to use git >> > > It seems to be a reasonable solution for those individuals who want to use > git, but in my experience not for organizations that want to use git, e.g. > have a local server with local

fly language <flylanguage at gmail.com> writes: >> After git, mainline will still be the most important branch for the >> *project*, >> but you will work with quite a few branches on parallel. >> >> > Who's mainline? :) Be prepared to assign a super-merger, like Linus, to > maintain the "mainline". > > The git workflow works really

On Jul 22, 2011, at 3:45 PM, Bob Wilson wrote: > > On Jul 22, 2011, at 3:33 PM, fly language wrote: > >> >> After git, mainline will still be the most important branch for the *project*, >> but you will work with quite a few branches on parallel. >> >> >> Who's mainline? :) Be prepared to assign a super-merger, like Linus, to maintain the

I attach a basic State of Art: ########################################################################################################################################## # State of Art Analysis of Git vs SVN ########################################################################################################################################## Scopus Keywords: GIT AND SVN

> After git, mainline will still be the most important branch for the > *project*, > but you will work with quite a few branches on parallel. > > Who's mainline? :) Be prepared to assign a super-merger, like Linus, to maintain the "mainline". The git workflow works really really great, but it does require getting rid of mainline thinking. It doesn't exist.

> > > Besides, the git-svn readonly bridge is a great solution for those who want > to use git > It seems to be a reasonable solution for those individuals who want to use git, but in my experience not for organizations that want to use git, e.g. have a local server with local branches, with many people banging on that while at the same time continuously merging the LLVM mainline

UNBIASED FACTS: ? Bugzilla & R-devel Mailing Lists: Remain unchanged: Understood as Ticketing platforms for bug pull requests on the R-devel Git Repository. ? Git Repository Options: A) Github (Cloud with Automated backups from GitHub to CRAN Server): https://github.com B) Gitlab (Selfhosted on CRAN): https://about.gitlab.com C) Phabricator (Selfhosted on CRAN): https://www.phacility.com D)

On Jul 22, 2011, at 12:29 AM, Matthieu Moy wrote: > Andrew Trick <atrick at apple.com> writes: > >> SVN revision numbers are central to my workflow. I use them to tag >> results generated against various builds. I like those results sorted >> by time and the chronology should be obvious, > > This means in the presence of branches, you want the ordering to be

Le 3 sept. 2011 à 14:18, Bill Wendling a écrit : > On Sep 3, 2011, at 5:01 AM, FlyLanguage wrote: > >>> On Sep 1, 2011, at 3:15 PM, FlyLanguage wrote: >>> >>>>> Is that really true? I've heard of a lot of LLVM developers using git >>>>> but it all seems very opaque right now. That's why I hope to get people >>>>>

On Sat, Mar 27, 2010 at 4:38 PM, Michel Alexandre Salim <michael.silvanus at gmail.com> wrote: >> git svn clone --no-minimize-url -s http://llvm.org/svn/llvm-project/llvm llvm > Initialized empty Git repository in /home/inf2/i2staff/salim/checkout/llvm/.git/ > RA layer request failed: Server sent unexpected return value (403 > Forbidden) in response to REPORT request for >