search for: dcommits

Tobias Grosser <tobias at grosser.es> writes: >> Will git-cherrypick work or is the merging process going to confuse >> git-svn? > > To use git-svn you should always have a history without any git > merges. Just commit after commit after commit. I do not know what kind > of history git-cherrypick produces. To clarify, I just need to create the branch at the point

On 07/06/2011 07:53 AM, David A. Greene wrote: > Tobias Grosser<tobias at grosser.es> writes: > >>> Will git-cherrypick work or is the merging process going to confuse >>> git-svn? >> >> To use git-svn you should always have a history without any git >> merges. Just commit after commit after commit. I do not know what kind >> of history

Rafael Ávila de Espíndola <rafael.espindola at gmail.com> writes: > On 07/05/2011 03:27 PM, David Greene wrote: >> My git-svn fu is not very strong. >> >> In the course of preparing a set of AVX patches, I've committed several >> changes to my local LLVM git clone. I don't want to send all of those >> changes upstream right away. What's the

My git-svn fu is not very strong. In the course of preparing a set of AVX patches, I've committed several changes to my local LLVM git clone. I don't want to send all of those changes upstream right away. What's the best way to send just the first of those changes us using git-svn? dcommit appears to send all pending changes. Is there a way of branching/cherry-picking that will

On 07/05/2011 03:48 PM, David A. Greene wrote: > Rafael Ávila de Espíndola<rafael.espindola at gmail.com> writes: > >> On 07/05/2011 03:27 PM, David Greene wrote: >>> My git-svn fu is not very strong. >>> >>> In the course of preparing a set of AVX patches, I've committed several >>> changes to my local LLVM git clone. I don't want to

Dave, bty, don't you work on your branches, but master? I think it would be not "the right git way". ...Takumi ps. for me, to commit much commits; $ git checkout master $ git rebase -i mybranch (pick up commits interactive on master as cherry) $ make -C builddir check-all -j4 $ git svn dcommit -n

On 07/05/2011 03:27 PM, David Greene wrote: > My git-svn fu is not very strong. > > In the course of preparing a set of AVX patches, I've committed several > changes to my local LLVM git clone. I don't want to send all of those > changes upstream right away. What's the best way to send just the first > of those changes us using git-svn? dcommit appears to send all

Folks, I'm now using the git mirror, but I'm not sure how to commit changes via git, if at all possible. So far, I'm diffing & applying it on an RW svn tree and committing, but that makes me test twice and it's error prone. I read the manual regarding git-svn setup and all it has is the connection to svn to keep svn's linearity, but nothing on commit strategy. With git,

On Mon, Dec 31, 2012 at 4:56 PM, Renato Golin <rengolin at systemcall.org> wrote: > With git, I normally issue a pull request, but in LLVM, this won't > work. Is there a FAQ/doc/manual on how to do that or what are the best > practices when working with git? Basically, once you are set up with git-svn (see

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 >

Erik> I am surprised noone has mentioned the one of the biggest Erik> advantages of Git which is proper author attribution for Erik> non-core and drive-by patch contributors. >From what I can make of the git-svn docs, that LLVM committers should be adding a "From: <email>" field to commit messages instead of "Patch by <name>". If the original author is

Hello Everyone, It seems given the decent amount of discussions it's time to make small announcement. So, official git mirrors are available for some subset of LLVM projects. They were used by some LLVM developers for couple of months already and seem to be stable enough. Right now there is a mirroring for LLVM itself and clang. More can be added per requests. The mirrors are made via

I've been using Jakob's commands below, but it has stopped working for me. This happened roughly around the time when Anton added the other branches, but I'm not sure if that was the cause or not. The symptom is that the "git svn rebase -l" command does nothing except say that the master branch is already up to date, and "git svn dcommit" complains that files are

On Feb 1, 2011, at 12:20 PM, Anton Korobeynikov wrote: > Hello Everyone, > > It seems given the decent amount of discussions it's time to make > small announcement. > > So, official git mirrors are available for some subset of LLVM > projects. They were used by some LLVM developers for couple of months > already and seem to be stable enough. Thank you for setting

On 1 January 2013 00:52, Sean Silva <silvas at purdue.edu> wrote: > Basically, once you are set up with git-svn (see > <http://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-git-svn>), > all you have to do is `git svn dcommit`. Oh, the docs do mention "dcommit" en passant, but nothing explicit. > 1. checkout master and pull from origin. > 2.

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

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

On Jul 23, 2011, at 5:37 AM, FlyLanguage wrote: > Yes, but who's mainline? Is the plan to have a centralized repo with a mainline branch that everybody pushes to, or the a linux style model where some person has an official mainline to which he pulls? > > It's quite different things. >From my interpretation of what Chris has said about this, it would be the former

Good evening, Jay! ...Instructions, ... 1. git clone http://llvm.org/git/XXX.git (assume it "origin") 2. Create git authors file (assume /path/to/file/of/authors) with single line. foad = Jay Foad <jay.foad at gmail.com> Oh yeah, you should define your name and mailto same as described in llvm.org/git with case-sensitive. 3. Edit .git/config manually :p [svn]

> > > 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