[git-users] Re: The remote end hang up unexpectedly
Greetings, the x is random, sometimes you have to try 5 times or 12 time or 20 times The server is clean, as we can see. No errors in the logs. We did a tcpdump already, even this seems clean and looks like a normal disconnect. I attached some traces an debug-outputs from ssh. Could it be an incompatibility with ssh? We are on Debian 5 with all patches. Should we try an upgrade to 6? -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/KOpJ4ThpDz8J. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en. GIT_TRACE=1 git push -v trace: built-in: git 'push' '-v' Pushing to git@git:/daten/git/dbc.git trace: run_command: 'ssh' 'git@git' 'git-receive-pack '\''/daten/git/dbc.git'\''' debug2: ssh_connect: needpriv 0 debug1: Connecting to git [192.168.0.251] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5 debug1: match: OpenSSH_5.1p1 Debian-5 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 831 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server-client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 855 debug2: dh_gen_key: priv key bits set: 128/256 debug2: bits set: 510/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 999 debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts debug3: check_host_in_hostfile: match line 22 debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts debug3: check_host_in_hostfile: match line 21 debug1: Host 'git' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:22 debug2: bits set: 515/1024 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 1015 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received
[git-users] Re: excludesfile on Windows
Hi Alexander, Aha, I see. No, keeping a certain set of files from being merged is not possible in any straight forward way. It is usually a sign that your code does not have quite the right structure for its task. Basically, code that you don't want to be merged along with the rest of your changes should somehow be kept outside the current Git repository. Let's say your project is called funky, and you want to keep the code excluded from merging in a separate repo called funky-private: ├── funky │ └── stuff.txt └── funky-private └── TODO.txt Once you get your private code (that is, your TODO.txt) file into funky-private, you can pick some way of including it into the first one during development, build, or run-time like this: ├── funky │ ├── private - ../funky-private │ │ └── TODO.txt │ └── stuff.txt └── funky-private └── TODO.txt Either use some way of linking in the directoryhttp://superuser.com/questions/234422/does-windows7-support-symbolic-links-folder-shortcuts, copy it in using some script, and then ignore this folder (here called * private*) in funky/.gitignore. Or use submodules as suggested in that thread on stackoverflow you mentioned. It depends on your workflow, and what you persona preferences. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/7iv5R6AcfDkJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] Re: The remote end hang up unexpectedly
Indeed, the logs you posted don't tell me much. Indeed, it appears as if the ssh client closes the connection and sends an error code upstream, probably because the server doesn't ack the close (I'm speculating...). Maybe the following questions need also be answered before trying anything else: - Does this happen on other machines running the same software? - Would it be possible to set up a direct network link between client and server (i.e. no network switches, etc.) and retry? I'm maintaining my opinion that this is a network-related problem rather than a git-related one. One other thing to check, if you're using consumer-grade network switches between your client ad the server is that the MTUs for the eth interfaces on both client and server do not exceed 1500. Cheap network switches simply discard any packet larger than this. Yeah, toy with the MTU... -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/7NDflXWlo0MJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] Re: The remote end hang up unexpectedly
Both the server and the client are virtual machine in VMware. But both run on the same physical machine, so there is no physical switch between the machines. I've migrated one of them onto another physical machine, maybe this helps. The switches are HP ProCurve 2900, MTU is 1500 everywhere, even on the vm-switches, no jumboframes... So i have to install two new servers and test, okay... -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/RZ7nIOcN45MJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] Re: The remote end hang up unexpectedly
Yeah, I'd definitely do that, especially since it should be as easy as moving .vmx files between physical machines that are already connected. I'd not rely upon the wm-switches for anything more complex than ftp-ing between VMs... I fear they were not even tested for doing more than just that... I've had my own share of trouble with VMWare. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/lUGzs0M3L3IJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] Git Local files to add on server..
I have installed Git on my computer, but my projects are saved on a server (long story as to why but is a legacy thing that I can't change) can I use Git like that, or do I need to install it on the server? -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/SzuBYO5EdzUJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] about git format-patch help
In my tree from git log I can see the last commit commit 1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6 Author: Mathieu Desnoyers mathieu.desnoy...@polymtl.ca Date: Fri Sep 3 08:08:18 2010 -0400 LTTng modularization, import of lttng 0.226 Will match kernel tree lttng 0.227. Signed-off-by: Mathieu Desnoyers mathieu.desnoy...@efficios.com to get the patch I run lyang0@lyang0-OptiPlex-755:~/git/lttng-modules$ git format-patch 1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6^..1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6 fatal: ambiguous argument '1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6^..1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6': unknown revision or path not in the working tree. Use '--' to separate paths from revisions for other commit it works fine lyang0@lyang0-OptiPlex-755:~/git/lttng-modules$ git format-patch f277b4c1b33341d2e687a614739778084de370d4^..f277b4c1b33341d2e687a614739778084de370d4 0001-Support-architectures-without-dump-tables.patch To reproduce it you can run git clone git://git.lttng.org/lttng-modules.git git format-patch 1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6^..1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6 Thanks Lei -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/k16YWOs_hesJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
Re: [git-users] How to share branch?
Thanks Vineet for your reply. It works now. BR Sandy -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/QB2plqK-p28J. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
Re: [git-users] cannot spawn ssh while trying to push changes to remote (e.g. github)
Ok so I have tried to do this *plink x...@github.com git --version * but I have received this error : *C:\Users\XXXplink x...@github.com git --version FATAL ERROR: Disconnected: No supported authentication methods available (server sent: publickey)* * * When I set my *GIT_SSH* to *C:\Putty\ * (where I have plink.exe) (I have also added *C:\Putty\* to *PATH ) *then I get this on *git clone * * * *$ GIT_TRACE=1 git clone g...@github.com:XXX/AffableBean trace: built-in: git 'clone' 'g...@github.com:XXX/AffableBean' Cloning into 'AffableBean'... trace: run_command: 'C:\Putty\' 'g...@github.com' 'git-upload-pack '\''XXX /AffableBean'\''' error: cannot spawn C:\Putty\: No such file or directory fatal: unable to fork* What other information should I provide ? 2012/6/13 Konstantin Khomoutov flatw...@users.sourceforge.net On Wed, 13 Jun 2012 03:49:23 -0700 (PDT) Patryk Małek malekpat...@gmail.com wrote: I have a problem with github - namely I cannot push changes to remote server i.e. github because I always get cannot spawn ssh/plink etc etc errors . I am using Win7 (git installation with separate bash ) and I have been already trying many things with e.g. environment variables ( GIT_SSH ) . I have even created a topic on www.stackoverflow.com but noone was able to help me. http://stackoverflow.com/questions/10574267/cannot- spawn-ssh-when-connecting-to-github-but-ssh-t-gitgithub-com-works I have used ssh installed with git or e.g. plink from putty's package but none of these worked . I have tried setting GIT_SSH to executables and then to directories with executables but none of these worked either. I know that there is an issue with directories with spaces so I placed exes to C:\Putty\ but still no go. Please help me because I really want to try Git but I cannot even start since I have this problem. Cc-ing to the msysgit mailing list as this question most probably belongs there. Please provide exact description of your setup, what commands you run and what output they provide (copy and paste exactly). Better run the commands with GIT_TRACE environment variable set to 1 beforehand to produce verbose output. Note that your post is too inconstructive as it sounds like I've tried a number of different combinations of different settings, none worked. Working with remote repos works for many people both with packaged OpenSSH client and with plink.exe from PuTTY, so try sticking to one solution and let's start from there. For instance, try sticking with PuTTY, verify the GIT_SSH environment variable is correctly set (to the full path to plink.exe, possibly double-quoted if PuTTY is installed under %ProgramFiles%), then verify plink.exe works for you outside or Git by running something like plink.exe you@git.server git --version Then re-try with Git, post what you run and what output you get. Provide detailed info about your OS. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
Re: [git-users] cannot spawn ssh while trying to push changes to remote (e.g. github)
Reading your post on StackOverflow, it looks to me like you are mixing Cygwin/Git Bash with normal Windows paths. I would suggest the following: 1. Start from scratch, remove all keys and software you set up/installed already. 2. Try Github for Windows http://windows.github.com/. If that works, at least you know it's physically possible to clone something from Github. 3. Now decide, as Konstantin says, whether you want to use *openssh* for authenticating (easier, and recommended by Github), or *Putty* (more Windows GUI oriented) - If you go for the openssh way, follow Github's how-tohttps://help.github.com/articles/set-up-git#platform-windows . - If you go for the Putty approach, follow my guide herehttp://blog.tfnico.com/2012/04/my-git-setup-on-windows.html , - Whichever approach you pick, follow the instructions to the letter, and tell us where it goes wrong, if at all. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/B_93b3K15ygJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
Re: [git-users] cannot spawn ssh while trying to push changes to remote (e.g. github)
On Wed, 13 Jun 2012 14:30:27 +0200 Patryk Małek malekpat...@gmail.com wrote: Ok so I have tried to do this *plink x...@github.com git --version * but I have received this error : *C:\Users\XXXplink x...@github.com git --version FATAL ERROR: Disconnected: No supported authentication methods available (server sent: publickey)* This means github only supports public-key-based authentication (the SSH protocol specifies at least three other, including a widely-known password-based). Since you did not add your github key to your SSH key agent (pageant.exe from PuTTY), plink saw no usable key and hence failed to authenticate you. I somehow feel this will be the next obstacle you will run into so after you fix GIT_SSH (we'll get to that in a moment), be sure to read [1] which deals with generating and using SSH keys via PuTTY and [2] which deals with associating those keys with your github account. When I set my *GIT_SSH* to *C:\Putty\ * (where I have plink.exe) (I have also added *C:\Putty\* to *PATH ) *then I get this on *git clone * * * *$ GIT_TRACE=1 git clone g...@github.com:XXX/AffableBean trace: built-in: git 'clone' 'g...@github.com:XXX/AffableBean' Cloning into 'AffableBean'... trace: run_command: 'C:\Putty\' 'g...@github.com' 'git-upload-pack '\''XXX /AffableBean'\''' error: cannot spawn C:\Putty\: No such file or directory fatal: unable to fork* Well, Git precisely tells you what happened: it failed to execute C:\Putty\. Does attempt to execute a directory appear to be OK to you? It shouldn't. As I've told you in my previous response, the GIT_SSH environment variable has to be set to the full pathname of the plink.exe binary which is (probably) C:\Putty\plink.exe in your particular case. What other information should I provide ? That's already enough. 1. http://nathanj.github.com/gitguide/tour.html#pushing 2. https://help.github.com/articles/generating-ssh-keys -- You received this message because you are subscribed to the Google Groups Git for human beings group. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
Re: [git-users] Git Local files to add on server..
On Wed, 13 Jun 2012 02:11:51 -0700 (PDT) Flashman pa...@derwentdata.com wrote: I have installed Git on my computer, but my projects are saved on a server (long story as to why but is a legacy thing that I can't change) can I use Git like that, or do I need to install it on the server? Uh... like what? Do you mean somehow accessing the server's file sysem (exported using NFS or CIFS or whatever file sharing protocol)? If so then yes, that is theoretically possible but it's highly recommended against for any practical use. Sensible objections include: * Git is super-fast, but this means super-fast when dealing with local files on a fast storage. By breaking this assumption you deprive yourself of this advantage Git can give you. * Working with remote files does have certain inherent problems: NFS is widely beleived to provide crappy locking (which does not work OK in certain circumstances). Problems with working over CIFS have been reported for Git for Windows, and they're unlikely to be dealt with as this is not a problem for those who are able to fix it. * You lose that every repository is a backup advantage, too: should your server's FS trash, you won't have a local repository copy. Next, if you will decide to go for normal Git workflow (you really should), you *will* need to have Git on the server: no matter what transport protocol is used to access the server-side Git instance, in the end, your local Git process always talks to a Git process running on the server. To minimize the required amount of file transfers, I would go for this solution: 1) Install Git on the server. Verify it works (it can be accessed by the protocol(s) of your choice, both fetching and pushing works). 2) Create a repository on the server. The server usually hosts the so-called bare repositories, and adding files to such a repository requires a bit of extra work as you'll need to use a detached work tree, but it's doable, see below. 3) After recording an initial commit in the repository, clone it to your client. Below is explained how to create an initial commit in a bare repository. Suppose you have a directory ~/devel/project which you want to turn into a server-side (bare) Git repo. 1) Create the repo: $ mkdir ~/devel/project.git cd $_ $ git init --bare And make Git know where our repo is located: $ export GIT_DIR=~/devel/project.git 2) Create a directory for the throw-away work tree: $ mkdir /tmp/worktree cd $_ And make Git know where our work tree is located: $ export GIT_WORK_TREE=`pwd` 3) Populate it with our project files: $ cp -R -l ~/devel/project/* . Then add everythhing: $ git add . (Here you'll probably need to tinker with the added files until you're happy with what will be committed.) Then commit: $ git commit -m Initial commit 4) Get rid of the work tree: $ cd rm -rf $GIT_WORK_TREE At this point you can return back into your $GIT_DIR and run `git branch` and `git log` there to see that you have recorded an initial commit on branch master. Now on your client you can do $ git clone ssh://you@git.domain.local/~/devel/project.git and see your repo cloned into the project directory. You can repeat this step for any repo you need to create on the server. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
Re: [git-users] about git format-patch help
On Wed, 13 Jun 2012 02:32:25 -0700 (PDT) lei yang yanglei.f...@gmail.com wrote: In my tree from git log I can see the last commit commit 1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6 Author: Mathieu Desnoyers mathieu.desnoy...@polymtl.ca Date: Fri Sep 3 08:08:18 2010 -0400 LTTng modularization, import of lttng 0.226 Will match kernel tree lttng 0.227. Signed-off-by: Mathieu Desnoyers mathieu.desnoy...@efficios.com to get the patch I run lyang0@lyang0-OptiPlex-755:~/git/lttng-modules$ git format-patch 1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6^..1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6 fatal: ambiguous argument '1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6^..1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6': unknown revision or path not in the working tree. Use '--' to separate paths from revisions [...] I think you'd better post this to the main Git list (git at vger.kernel.org, you can subscribe to it at [1]) as this might indicate a bug. To try to solve the problem at hand: does git format-patch -1 1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6 work for you? According to the docs, this has to export the changeset of just the single indicated commit. 1. http://vger.kernel.org/vger-lists.html -- You received this message because you are subscribed to the Google Groups Git for human beings group. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
Re: [git-users] Official mailing list e-mail for questions and comments doesn't work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11.06.2012 22:00, Erlend Sogge Heggen wrote: Aaaah, it probably came down to some simple use of rich text, yeah. Well, I got a working link and the rest of the problem is known, so that about covers it. Thanks! You're welcome :) - -- [Mika Suomalainen](https://mkaysi.github.com/) || [gpg --keyserver pool.sks-keyservers.net --recv-keys 4DB53CFE82A46728](http://mkaysi.github.com/PGP/key.txt) || [Why do I sign my emails?](http://mkaysi.github.com/PGP/WhyDoISignEmails.html) || [Please don't send HTML.](http://mkaysi.github.com/articles/complaining/HTML.html) || [This signature](https://gist.github.com/2643070#file_icedove.md) || [Please reply below this line](http://mkaysi.github.com/articles/complaining/topposting.html) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Homepage: http://mkaysi.github.com/ Comment: gpg --keyserver pool.sks-keyservers.net --recv-keys 82A46728 Comment: Public key: http://mkaysi.github.com/PGP/key.txt Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP2LhbAAoJEE21PP6CpGcoKX0QAIHUeh7z19D43LeBPRCEnFK1 J2F4351PHSBDeCwTHWtDf3mEBH2Kog1PzL6KAJ/VUv3wWllhux8zM2OIY/w7bsHp AQN03UqkfLPDfkD6SkhzGaNodn5OpAQr+9ubrcXVWZKDqqox+UtWh3M6Qk7dhdxq SmYEM+NWH2+CpvbnUTJH0PPTigqXjhN4D1naXgg6/xUybfi6QdthQjsGM2YPft/g jQpGeN5Hiwu29W1MhWGtKW9JndyS7siyCMQCfhYSXnVNX8Kc67bIz3D1bM2djgfd OkOZE1rNfNj75eQbaGN7Q+ziiQh8266TN7zGLd7m+FMALjZGBdsJIc8OiX+Lwp3u x7H7Z/sqCdGhDR5HCy21/hj/2DdLPBBZDedhLQCWIFLNJocFL3S6nirSVwTuJq+A S4Tgln0UalPnZDRAQJp55Ze20NL5BBds+pRTw/XyOeiqEbjOng7ifxXXn6A9HIMS /ZjA1MMW+1H+NahKE22kwdj2/lR3CwPLDvQeOH2gUyXgn1m9up2QDGviDl7/IiZG 12LlSCu0lsDnUlOnTLnkTDt2/8Yq47Z3xx1JYvWekJKMEcug6CfmZdz0SxMuLZ5A /FiAaOU7aIErsxvItMLFc2smru00J3mIxjAgcpm58NZYk58NxVWGUxTIDWyiL+hZ pz0LNFTkbolv0qF4h0Wk =BDKt -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups Git for human beings group. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
Re: [git-users] about git format-patch help
On Wed, Jun 13, 2012 at 11:25 PM, Konstantin Khomoutov flatw...@users.sourceforge.net wrote: On Wed, 13 Jun 2012 02:32:25 -0700 (PDT) lei yang yanglei.f...@gmail.com wrote: In my tree from git log I can see the last commit commit 1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6 Author: Mathieu Desnoyers mathieu.desnoy...@polymtl.ca Date: Fri Sep 3 08:08:18 2010 -0400 LTTng modularization, import of lttng 0.226 Will match kernel tree lttng 0.227. Signed-off-by: Mathieu Desnoyers mathieu.desnoy...@efficios.com to get the patch I run lyang0@lyang0-OptiPlex-755:~/git/lttng-modules$ git format-patch 1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6^..1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6 fatal: ambiguous argument '1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6^..1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6': unknown revision or path not in the working tree. Use '--' to separate paths from revisions [...] I think you'd better post this to the main Git list (git at vger.kernel.org, you can subscribe to it at [1]) as this might indicate a bug. To try to solve the problem at hand: does git format-patch -1 1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6 work for you? it did create a patch, but I dump this patch with nothing, git show 1c8284ebdbd119314b8f01e442e64cf5fd4b9fe6 is not null Lei According to the docs, this has to export the changeset of just the single indicated commit. 1. http://vger.kernel.org/vger-lists.html -- You received this message because you are subscribed to the Google Groups Git for human beings group. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] how to change the whole git tree to the patchsets
Hi list I want to change my whole tree to the patchset? which cmd can be used ? Lei -- You received this message because you are subscribed to the Google Groups Git for human beings group. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
Re: [git-users] how to change the whole git tree to the patchsets
On Thu, 14 Jun 2012 01:03:27 +0800 lei yang yanglei.f...@gmail.com wrote: I want to change my whole tree to the patchset? which cmd can be used ? git format-patch --root Did you RTFM? -- You received this message because you are subscribed to the Google Groups Git for human beings group. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
