similar to: git pull != svn update ?

I'm still not sure how I did it, but I managed to use the link http://wiki.winehq.org/GitWine for the latest development version, and even installed git (blind man navigating New York City streets). So now all I have to do is Code: git fetch ; git rebase origin to stay up to date. My question is how do I run programs with it? When I do the normal Code: wine setup.exe for example, it says

Hi everyone, I tried to clone the git mirrors and set up git-svn metadata according to these instructions: http://llvm.org/docs/GettingStarted.html#git-mirror Importantly, I did this (replacing <username>, of course): % git svn init https://llvm.org/svn/llvm-project/llvm/trunk --username=<username> % git config svn-remote.svn.fetch :refs/remotes/origin/master % git svn rebase -l #

I downloaded Wine sources using git-gui, compiled it and it worked great. Then I wanted to update it, so I run sudo make uninstall, then in git-gui I did remote - fetch from origin. Then I did ./configure make depend make -j4 sudo make install And when I checked the version with wine --version, it gave me the old one wine-1.1.5-399-g82f77cc instead of wine-1.1.5-xxx-g3a2dda1 where

Hello. My question may be more git-related that wine-related, sorry for that but I have much trouble finding an answer. I have retrieved yesterday's git, but it introduced a bug that stops wine from starting. I want to revert to 0.9.56 using this same tree, how can I do that? I tried 'git branch wine-0.9.56;git rebase origin' but it didn't work. Thanks. --

greened at obbligato.org (David A. Greene) writes: > Actually git pull can sometimes get you into trouble. Probably git > fetch / git rebase is the better combination for LLVM. I don't get it. Doesn't "git pull --rebase" do exactly a fetch followed by a rebase? -- Matthieu Moy http://www-verimag.imag.fr/~moy/

Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> writes: > greened at obbligato.org (David A. Greene) writes: > >> Actually git pull can sometimes get you into trouble. Probably git >> fetch / git rebase is the better combination for LLVM. > > I don't get it. > > Doesn't "git pull --rebase" do exactly a fetch followed by a rebase? No. It does

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

Hi. Ive used git for some time to download an update wine sources. However, Ive notices a couple of things i dont understand quite much. My general procedure to download sources and compile is this: git clone git://source.winehq.org/git/wine.git ~/wine-git cd ~/wine-git ./configure --prefix=/usr make sudo checkinstall --fstrans=no --pkgversion=1.1.12 Here I've noticed that I have to

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

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

David, A few comments. > Naming Upstream > --------------- > > The intial clone from upstream results in a git remote reference with > the rather unhelpful name of "origin." As more remote sources get > added, it is easy to forget what "origin" is. Therefore, add a remote > with a more descriptive name. > > git remote add llvm-upstream

On Fri, Jun 6, 2008 at 4:40 PM, Axel Gembe <ago at bastart.eu.org> wrote: > Well, just a simple helper. > > Signed-off-by: Axel Gembe <ago at bastart.eu.org> Axel, this looks like the output of git. How is that working out? Would you care to share some details on your setup? thanks, -- - Charles Lepple

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 Mar 21, 2011, at 1:47 PM, Bob Wilson wrote: > 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

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

On 03/21/2011 04:54 PM, Jakob Stoklund Olesen wrote: > > On Mar 21, 2011, at 1:47 PM, Bob Wilson wrote: > >> 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

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

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

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]

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