search for: git_mirror

...1 15:50, Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> wrote: > I guess you have to rebase (pull --rebase or so) your branches. "git > rebase" is relatively smart, and will skip patches that you already have > in your local branch. http://llvm.org/docs/GettingStarted.html#git_mirror "Since the upstream repository is in Subversion, you should use "git pull --rebase" instead of "git pull" to avoid generating a non-linear history in your clone." cheers, --renato

We are using git internally at MIPS now for LLVM work. I'm assuming others are too. What tools/workflows are people using to merge the changes back to svn for a patch? Thanks in advance. Reed

dag at cray.com (David A. Greene) writes: > But none of this explains how to prevent false conflicts when updating > your git workarea from the svn git mirror. The problem is that dcommit > changes the hash from what's in your local repository to something > different. When you then update from the git mirror, you get a conflict > because two commits with different hashes

Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> writes: > dag at cray.com (David A. Greene) writes: > >> Jason Kim <jasonwkim at google.com> writes: >> >>> I believe git has a similar system for maintaining "branches of patches"  >> >> A pointer/tutorial on how to do this would be most welcome. > > It depends on the definition of

Hi, This document tells me how to do a "read-only GIT clone of LLVM": http://llvm.org/docs/GettingStarted.html#git_mirror Can someone please document how to get read-write access using git or git-svn, if it's possible? Or do I still have to use plain old svn to commit? (I have tried searching the mailing list to find out how to do this, but it seems like a lot of the information there is out of date.) Thanks, Ja...