From: Stepan D. <stp...@na...> - 2013-06-10 18:06:10
|
Hello Borja, Git allows you to clone LLVM project (it has GIT mirror), and develop your backend in your own branch. You will *never* lose commits under git, since it is distributed VCS and everyone keeps clone of all project history. There is good one-day git tutorial: http://git-scm.com/documentation -Stepan. Borja Ferrer wrote: > Ok then, guys that have used GIT before please discuss any advantages > here. As i said, i havent used GIT before so i can't add any valuable > points. I've been able to work with SVN and LLVM quite well so far though. > > > 2013/6/10 Weddington, Eric <Eri...@at... > <mailto:Eri...@at...>> > > > > > -----Original Message----- > > From: Borja Ferrer [mailto:bor...@gm... > <mailto:bor...@gm...>] > > Sent: Monday, June 10, 2013 11:33 AM > > To: Stepan Dyatkovskiy; Weddington, Eric > > Cc: avr...@li... > <mailto:avr...@li...> > > Subject: Re: [avr-llvm-devel] Fwd: Sync with trunk > > > > Eric, what do you exactly mean? Trunk changes in LLVM are > automatically > > merged in your local repo when you update, and when we need to update > > our code base to fix interface changes we have to do it manually but > > that's the only way I know of. > > All I'm trying to figure out is what would be the best VCS for us to > use (svn or git) in moving over to Atmel Spaces. If using one over > the other makes it easier to do some tasks (like staying in sync > with llvm trunk), then we should go with the one that makes it easier. > > If it doesn't really matter, then I suggest just sticking with svn. > > Eric > > |