{"thread":{"id":"8678","subject":"problem pushing repository","startedAt":"2007-06-22T01:49:25Z","lastAt":"2007-06-25T01:01:47Z","messageCount":15,"participants":["Adam Mercer","Junio C Hamano","Andrew Ruder","Raimund Bauer","Johannes Sixt","Johannes Schindelin","Shawn O. Pearce","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"45536","messageId":"799406d60706211849h6e4fd1dbn487beab03fe1d79c@mail.gmail.com","threadId":"8678","inReplyTo":null,"subject":"problem pushing repository","fromName":"Adam Mercer","fromEmail":"ramercer@gmail.com","sentAt":"2007-06-22T01:49:25Z","receivedAt":"2007-06-22T01:49:25Z","isPatch":false,"sender":{"key":"ramercer@gmail.com","avatar":"https://gravatar.com/avatar/16dc719817f62b75075d529ce4ea992ee82bb1a08e45a3029797f39223d6ee64?d=mp&s=160"},"body":"Hi\n\nI've just started using git to track a project I'm working on and I'm\nhaving a problem pushing my repository.\n\n[ram@skymoo glue]$ git push\nssh://ram@newberry.ihepa.ufl.edu/~ram/public_html/git/glue.git\nbash: line 1: git-receive-pack: command not found\nfatal: The remote end hung up unexpectedly\nerror: failed to push to\n'ssh://ram@newberry.ihepa.ufl.edu/~ram/public_html/git/glue.git'\n[ram@skymoo glue]$ which git-receive-pack\n/Users/ram/opt/git/bin/git-receive-pack\n[ram@skymoo glue]$\n\ngit-receive-pack is in my $PATH so why can't it be found when trying to push?\n\nCheers\n\nAdam\n"},{"id":"45537","messageId":"7v8xacbvf1.fsf@assigned-by-dhcp.pobox.com","threadId":"8678","inReplyTo":"799406d60706211849h6e4fd1dbn487beab03fe1d79c@mail.gmail.com","subject":"Re: problem pushing repository","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-06-22T02:00:18Z","receivedAt":"2007-06-22T02:00:18Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Adam Mercer\" writes:\n\n> [ram@skymoo glue]$ git push\n> ssh://ram@newberry.ihepa.ufl.edu/~ram/public_html/git/glue.git\n> bash: line 1: git-receive-pack: command not found\n> fatal: The remote end hung up unexpectedly\n> error: failed to push to\n> 'ssh://ram@newberry.ihepa.ufl.edu/~ram/public_html/git/glue.git'\n> [ram@skymoo glue]$ which git-receive-pack\n> /Users/ram/opt/git/bin/git-receive-pack\n> [ram@skymoo glue]$\n>\n> git-receive-pack is in my $PATH so why can't it be found when trying to push?\n\nCheck your ssh and ssh server settings. Often the process\ninvoked from non-interactive ssh connection (such as the attempt\nto invoke receive-pack) would not get the PATH you set up in ~/.login\nor ~/.bash_profile.\n\n\t$ ssh newberry.ihepa.ufl.edu sh -c 'echo $PATH'\n\nmay be a good starting point to test this, and the first step\nto fix it would be\n\n\t$ man ssh\n\t$ man sshd\n"},{"id":"45538","messageId":"20070622022426.GA2961@bowser.ruder","threadId":"8678","inReplyTo":"7v8xacbvf1.fsf@assigned-by-dhcp.pobox.com","subject":"Re: problem pushing repository","fromName":"Andrew Ruder","fromEmail":"andy@aeruder.net","sentAt":"2007-06-22T02:24:26Z","receivedAt":"2007-06-22T02:24:26Z","isPatch":false,"sender":{"key":"andy@aeruder.net","avatar":"https://gravatar.com/avatar/cd5239f6d3c9acac61e817de7f7d497e518415e23720f170a10e0663a7981963?d=mp&s=160"},"body":"On Thu, Jun 21, 2007 at 07:00:18PM -0700, Junio C Hamano wrote:\n> \t$ ssh newberry.ihepa.ufl.edu sh -c 'echo $PATH'\n> \n> may be a good starting point to test this, and the first step\n> to fix it would be\n> \n> \t$ man ssh\n> \t$ man sshd\n\nWhile I wholeheartedly agree with Junio here, you may also find\n\nremote..receivepack\n\nuseful, see git-push(1) and git-config(1) for more information.\n\n- Andy\n\n-- \nAndrew Ruder \nhttp://www.aeruder.net\n"},{"id":"45554","messageId":"467B782E.84A6742F@eudaptics.com","threadId":"8678","inReplyTo":"799406d60706211849h6e4fd1dbn487beab03fe1d79c@mail.gmail.com","subject":"Re: problem pushing repository","fromName":"Johannes Sixt","fromEmail":"j.sixt@eudaptics.com","sentAt":"2007-06-22T07:20:14Z","receivedAt":"2007-06-22T07:20:14Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Adam Mercer wrote:\n> [ram@skymoo glue]$ git push\n> ssh://ram@newberry.ihepa.ufl.edu/~ram/public_html/git/glue.git\n> bash: line 1: git-receive-pack: command not found\n> fatal: The remote end hung up unexpectedly\n> error: failed to push to\n> 'ssh://ram@newberry.ihepa.ufl.edu/~ram/public_html/git/glue.git'\n> [ram@skymoo glue]$ which git-receive-pack\n> /Users/ram/opt/git/bin/git-receive-pack\n> [ram@skymoo glue]$\n> \n> git-receive-pack is in my $PATH so why can't it be found when trying to push?\n\nYou must have git installed on the remote end, too.\n\n-- Hannes\n"},{"id":"45553","messageId":"1182496916.6207.11.camel@localhost","threadId":"8678","inReplyTo":"20070622022426.GA2961@bowser.ruder","subject":"Re: problem pushing repository","fromName":"Raimund Bauer","fromEmail":"ray007@gmx.net","sentAt":"2007-06-22T07:21:56Z","receivedAt":"2007-06-22T07:21:56Z","isPatch":false,"sender":{"key":"ray007@gmx.net","avatar":null},"body":"On Thu, 2007-06-21 at 21:24 -0500, Andrew Ruder wrote:\n> On Thu, Jun 21, 2007 at 07:00:18PM -0700, Junio C Hamano wrote:\n> > \t$ ssh newberry.ihepa.ufl.edu sh -c 'echo $PATH'\n> > \n> > may be a good starting point to test this, and the first step\n> > to fix it would be\n> > \n> > \t$ man ssh\n> > \t$ man sshd\n> \n> While I wholeheartedly agree with Junio here, you may also find\n> \n> remote..receivepack\n\nYes, but it doesn't always work.\nI have a server with several repositories, and git is installed\nin /usr/local/bin.\nAll my local repostories know this server as a remote named 'slcom' and\nI have a 2 global options\nremote.slcom.uploadpack=/usr/local/bin/git-upload-pack\nremote.slcom.receivepack=/usr/local/bin/git-receive-pack\n\nFetching, pulling and normal pushing works.\nPushing a new branch to the remote doesn't work:\n$ git branch test\n$ git push slcom test:test \nerror: dst refspec test does not match any existing ref on the remote\nand does not start with refs/.\nfatal: The remote end hung up unexpectedly\nerror: failed to push to\n'ray@softwarelandschaft.com:/home/ray/repos/drupal/multirate'\n\ngit-remote also has a problem:\n$ git remote show slcom\nbash: git-upload-pack: command not found\nfatal: The remote end hung up unexpectedly\nls-remote --heads\nray@softwarelandschaft.com:/home/ray/repos/drupal/multirate: command\nreturned error: 1\n\nAll this with git from yesterday (next).\n\n> - Andy\n\n-- \nbest regards\n\n Ray\n"},{"id":"45561","messageId":"Pine.LNX.4.64.0706221224310.4059@racer.site","threadId":"8678","inReplyTo":"1182496916.6207.11.camel@localhost","subject":"Re: problem pushing repository","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-06-22T11:26:51Z","receivedAt":"2007-06-22T11:26:51Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Fri, 22 Jun 2007, Raimund Bauer wrote:\n\n> $ git push slcom test:test \n> error: dst refspec test does not match any existing ref on the remote\n> and does not start with refs/.\n> fatal: The remote end hung up unexpectedly\n> error: failed to push to\n> 'ray@softwarelandschaft.com:/home/ray/repos/drupal/multirate'\n\nThis is a completely unrelated problem!\n\nIt says that there is no branch named \"test\" on the remote side, and since \nyou could also want to push a tag, you have to say\n\n\ttest:refs/heads/test\n\nhere. However, I do not understand why you bother to use the :dst syntax \nhere, since your target name is _exactly_ the same as the source name. Why \nnot just\n\n\tgit push slcom test\n\nHm??\n\n> git-remote also has a problem:\n> $ git remote show slcom\n> bash: git-upload-pack: command not found\n> fatal: The remote end hung up unexpectedly\n> ls-remote --heads\n> ray@softwarelandschaft.com:/home/ray/repos/drupal/multirate: command\n> returned error: 1\n\nThat's apparently a bug in git-remote.\n\nCiao,\nDscho\n"},{"id":"45567","messageId":"799406d60706220623r17c0e3c6rca86a33d01ee6c7e@mail.gmail.com","threadId":"8678","inReplyTo":"7v8xacbvf1.fsf@assigned-by-dhcp.pobox.com","subject":"Re: problem pushing repository","fromName":"Adam Mercer","fromEmail":"ramercer@gmail.com","sentAt":"2007-06-22T13:23:49Z","receivedAt":"2007-06-22T13:23:49Z","isPatch":false,"sender":{"key":"ramercer@gmail.com","avatar":"https://gravatar.com/avatar/16dc719817f62b75075d529ce4ea992ee82bb1a08e45a3029797f39223d6ee64?d=mp&s=160"},"body":"On 21/06/07, Junio C Hamano wrote:\n> \"Adam Mercer\" writes:\n>\n> > [ram@skymoo glue]$ git push\n> > ssh://ram@newberry.ihepa.ufl.edu/~ram/public_html/git/glue.git\n> > bash: line 1: git-receive-pack: command not found\n> > fatal: The remote end hung up unexpectedly\n> > error: failed to push to\n> > 'ssh://ram@newberry.ihepa.ufl.edu/~ram/public_html/git/glue.git'\n> > [ram@skymoo glue]$ which git-receive-pack\n> > /Users/ram/opt/git/bin/git-receive-pack\n> > [ram@skymoo glue]$\n> >\n> > git-receive-pack is in my $PATH so why can't it be found when trying to push?\n>\n> Check your ssh and ssh server settings. Often the process\n> invoked from non-interactive ssh connection (such as the attempt\n> to invoke receive-pack) would not get the PATH you set up in ~/.login\n> or ~/.bash_profile.\n>\n> $ ssh newberry.ihepa.ufl.edu sh -c 'echo $PATH'\n>\n> may be a good starting point to test this, and the first step\n> to fix it would be\n>\n> $ man ssh\n> $ man sshd\n\nThanks Junio thats the problem my path isn't being set correctly on newberry\n\n[ram@skymoo ram]$ ssh newberry sh -c 'echo $PATH'\n\n[ram@skymoo ram]$ ssh newberry\n[ram@newberry ram]$ which git-receive-pack\n~/opt/git/bin/git-receive-pack\n[ram@newberry ram]$\n\nCheers\n\nAdam\n"},{"id":"45568","messageId":"799406d60706220636q4f7a3c17v6833d2eda25e8f0d@mail.gmail.com","threadId":"8678","inReplyTo":"20070622022426.GA2961@bowser.ruder","subject":"Re: problem pushing repository","fromName":"Adam Mercer","fromEmail":"ramercer@gmail.com","sentAt":"2007-06-22T13:36:50Z","receivedAt":"2007-06-22T13:36:50Z","isPatch":false,"sender":{"key":"ramercer@gmail.com","avatar":"https://gravatar.com/avatar/16dc719817f62b75075d529ce4ea992ee82bb1a08e45a3029797f39223d6ee64?d=mp&s=160"},"body":"On 21/06/07, Andrew Ruder wrote:\n> On Thu, Jun 21, 2007 at 07:00:18PM -0700, Junio C Hamano wrote:\n> > $ ssh newberry.ihepa.ufl.edu sh -c 'echo $PATH'\n> >\n> > may be a good starting point to test this, and the first step\n> > to fix it would be\n> >\n> > $ man ssh\n> > $ man sshd\n>\n> While I wholeheartedly agree with Junio here, you may also find\n>\n> remote..receivepack\n>\n> useful, see git-push(1) and git-config(1) for more information.\n\nThis seems like the best way to fix this issue, however it isn't clear\nfrom the man page what I need to put in my ~/.gitconfig. With the\nfollowing in .gitconfig\n\n[remote]\nglue.receivepack = /home/ram/opt/git/bin/git-receive-pack\n\nI get the following error when trying to push\n\n[ram@skymoo glue]$ git push\nssh://newberry.ihepa.ufl.edu/~/public_html/git/glue.git\nfatal: bad config file line 6 in /Users/ram/.gitconfig\n\nso this is clearly not the right entry. Can someone please give me a\npush in the right direction?\n\nCheers\n\nAdam\n"},{"id":"45569","messageId":"1182519484.6207.38.camel@localhost","threadId":"8678","inReplyTo":"Pine.LNX.4.64.0706221224310.4059@racer.site","subject":"Re: problem pushing repository","fromName":"Raimund Bauer","fromEmail":"ray007@gmx.net","sentAt":"2007-06-22T13:38:04Z","receivedAt":"2007-06-22T13:38:04Z","isPatch":false,"sender":{"key":"ray007@gmx.net","avatar":null},"body":"Hi,\n\nOn Fri, 2007-06-22 at 12:26 +0100, Johannes Schindelin wrote: \n> Hi,\n> \n> On Fri, 22 Jun 2007, Raimund Bauer wrote:\n> \n> > $ git push slcom test:test \n> > error: dst refspec test does not match any existing ref on the remote\n> > and does not start with refs/.\n> > fatal: The remote end hung up unexpectedly\n> > error: failed to push to\n> > 'ray@softwarelandschaft.com:/home/ray/repos/drupal/multirate'\n> \n> This is a completely unrelated problem!\n> \n> It says that there is no branch named \"test\" on the remote side, and since \n> you could also want to push a tag, you have to say\n> \n> \ttest:refs/heads/test\n> \n> here. However, I do not understand why you bother to use the :dst syntax \n> here, since your target name is _exactly_ the same as the source name. Why \n> not just\n> \n> \tgit push slcom test\n\nbecause I had gotten the command line from bash-completion and since it\nworked with existing branches I saw no reason why it shouldn't work with\nnew ones.\nwill read the documentation next time ;-)\n\n> Ciao,\n> Dscho\n\n-- \nbest regards\n\n Ray\n"},{"id":"45571","messageId":"1182521850.6207.42.camel@localhost","threadId":"8678","inReplyTo":"799406d60706220636q4f7a3c17v6833d2eda25e8f0d@mail.gmail.com","subject":"Re: problem pushing repository","fromName":"Raimund Bauer","fromEmail":"ray007@gmx.net","sentAt":"2007-06-22T14:17:30Z","receivedAt":"2007-06-22T14:17:30Z","isPatch":false,"sender":{"key":"ray007@gmx.net","avatar":null},"body":"On Fri, 2007-06-22 at 09:36 -0400, Adam Mercer wrote:\n> This seems like the best way to fix this issue, however it isn't clear\n> >from the man page what I need to put in my ~/.gitconfig. With the\n> following in .gitconfig\n> \n> [remote]\n> glue.receivepack = /home/ram/opt/git/bin/git-receive-pack\n\nIn my config it looks like this:\n\n[remote \"slcom\"]\n uploadpack = /usr/local/bin/git-upload-pack\n receivepack = /usr/local/bin/git-receive-pack\n\n-- \nbest regards\n\n Ray\n"},{"id":"45572","messageId":"799406d60706220732y76d94f07h54bbe9443a08f497@mail.gmail.com","threadId":"8678","inReplyTo":"1182521850.6207.42.camel@localhost","subject":"Re: problem pushing repository","fromName":"Adam Mercer","fromEmail":"ramercer@gmail.com","sentAt":"2007-06-22T14:32:38Z","receivedAt":"2007-06-22T14:32:38Z","isPatch":false,"sender":{"key":"ramercer@gmail.com","avatar":"https://gravatar.com/avatar/16dc719817f62b75075d529ce4ea992ee82bb1a08e45a3029797f39223d6ee64?d=mp&s=160"},"body":"On 22/06/07, Raimund Bauer wrote:\n\n> In my config it looks like this:\n>\n> [remote \"slcom\"]\n> uploadpack = /usr/local/bin/git-upload-pack\n> receivepack = /usr/local/bin/git-receive-pack\n\nputting\n\n[remote \"glue\"]\n uploadpack = /home/ram/opt/git/bin/git-upload-pack\n receivepack = /home/ram/opt/git/bin/git-receive-pack\n\nin my .gitconfig I still get the error saying that git-receive-pack\ncan't be found. If I specify the path on the git push command line\nusing the --exec option then git-receive-pack is found, so it appears\nthat my config file isn't being read.\n\nCheers\n\nAdam\n"},{"id":"45585","messageId":"20070622224712.GI17393@spearce.org","threadId":"8678","inReplyTo":"1182519484.6207.38.camel@localhost","subject":"Re: problem pushing repository","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-06-22T22:47:12Z","receivedAt":"2007-06-22T22:47:12Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Raimund Bauer wrote:\n> On Fri, 2007-06-22 at 12:26 +0100, Johannes Schindelin wrote: \n> > On Fri, 22 Jun 2007, Raimund Bauer wrote:\n> > \n> > > $ git push slcom test:test \n> > > error: dst refspec test does not match any existing ref on the remote\n> > > and does not start with refs/.\n> > \n> > It says that there is no branch named \"test\" on the remote side, and since \n> > you could also want to push a tag, you have to say\n> > \n> > \ttest:refs/heads/test\n> > \n> > here. However, I do not understand why you bother to use the :dst syntax \n> > here, since your target name is _exactly_ the same as the source name. Why \n> > not just\n> > \n> > \tgit push slcom test\n> \n> because I had gotten the command line from bash-completion\n\nI just patched the bash completion package to offer `git push slcom\ntest` as the completion, instead of `git push slcom test:test`.\nThe patch was pretty trivial, and is now also in my fastimport.git\ntree on repo.or.cz.\n\n-->8--\nAvoid src:dst syntax as default bash completion for git push\n\nRaimund Bauer just discovered that the default bash completion for\na local branch name in a git-push line is not the best choice when\nthe branch does not exist on the remote system.\n\nIn the past we have always completed the local name 'test' as\n\"test:test\", indicating that the destination name is the same as\nthe local name. But this fails when \"test\" does not yet exist on\nthe remote system, as there is no \"test\" branch for it to match\nthe name against.\n\nFortunately git-push does the right thing when given just the\nlocal branch, as it assumes you want to use the same name in the\ndestination repository. So we now offer \"test\" as the completion\nin a git-push line, and let git-push assume that is also the remote\nbranch name.\n\nWe also still support the remote branch completion after the :,\nbut only if the user manually adds the colon before trying to get\na completion.\n\nSigned-off-by: Shawn O. Pearce \n---\n contrib/completion/git-completion.bash | 2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash\nindex 9e72f0f..c7c9963 100755\n--- a/contrib/completion/git-completion.bash\n+++ b/contrib/completion/git-completion.bash\n@@ -683,7 +683,7 @@ _git_push ()\n \t\t\t__gitcomp \"$(__git_refs \"$remote\")\" \"\" \"${cur#*:}\"\n \t\t\t;;\n \t\t*)\n-\t\t\t__gitcomp \"$(__git_refs2)\"\n+\t\t\t__gitcomp \"$(__git_refs)\"\n \t\t\t;;\n \t\tesac\n \t\t;;\n-- \n1.5.2.2.1050.g51a8b\n\n-- \nShawn.\n"},{"id":"45597","messageId":"1182593536.5937.14.camel@localhost","threadId":"8678","inReplyTo":"20070622224712.GI17393@spearce.org","subject":"Re: problem pushing repository","fromName":"Raimund Bauer","fromEmail":"ray007@gmx.net","sentAt":"2007-06-23T10:12:16Z","receivedAt":"2007-06-23T10:12:16Z","isPatch":false,"sender":{"key":"ray007@gmx.net","avatar":null},"body":"Hi,\n\nOn Fri, 2007-06-22 at 18:47 -0400, Shawn O. Pearce wrote:\n> Signed-off-by: Shawn O. Pearce \n> ---\n> contrib/completion/git-completion.bash | 2 +-\n> 1 files changed, 1 insertions(+), 1 deletions(-)\n\nThanks a lot, your patch makes my life easier.\nSince you obviously know what you're doing here, maybe I can wish for\nsomething too?\n\nIt would be really cool if completion also worked when I started the\nbranchname with a '+' to force the push ...\n\n-- \nbest regards\n\n Ray\n"},{"id":"45719","messageId":"20070624234759.GO17393@spearce.org","threadId":"8678","inReplyTo":"1182593536.5937.14.camel@localhost","subject":"Re: problem pushing repository","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-06-24T23:47:59Z","receivedAt":"2007-06-24T23:47:59Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Raimund Bauer wrote:\n> On Fri, 2007-06-22 at 18:47 -0400, Shawn O. Pearce wrote:\n> > Signed-off-by: Shawn O. Pearce \n> > ---\n> > contrib/completion/git-completion.bash | 2 +-\n> > 1 files changed, 1 insertions(+), 1 deletions(-)\n> \n> Thanks a lot, your patch makes my life easier.\n> Since you obviously know what you're doing here, maybe I can wish for\n> something too?\n\nHeh, sure. I wrote that \"stock\" bash completion package, but at\nthis point I largely consider it to be \"complete and stable\" and\ntherefore don't put a lot of effort into it anymore.\n\nThis recent thread has been interesting, as it has uncovered two\nbugs related to the git-push completion.\n \n> It would be really cool if completion also worked when I started the\n> branchname with a '+' to force the push ...\n\nHow does this work? ;-)\n\nI'm pushing it out to my fastimport tree shortly.\n\n-->8--\nTeach bash how to complete +refspec on git-push\n\nUsing `git push origin +foo` to forcefully overwrite the remote\nbranch named foo is a common idiom, especially since + is shorter\nthan the long option --force and can be specified on a per-branch\nbasis.\n\nWe now complete `git push origin +foo` just like we do the standard\n`git push origin foo`. The leading + on a branch refspec does not\nalter the completion.\n\nSigned-off-by: Shawn O. Pearce \n---\n contrib/completion/git-completion.bash | 3 +++\n 1 files changed, 3 insertions(+), 0 deletions(-)\n\ndiff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash\nindex c7c9963..f2b10fa 100755\n--- a/contrib/completion/git-completion.bash\n+++ b/contrib/completion/git-completion.bash\n@@ -682,6 +682,9 @@ _git_push ()\n \t\t\tesac\n \t\t\t__gitcomp \"$(__git_refs \"$remote\")\" \"\" \"${cur#*:}\"\n \t\t\t;;\n+\t\t+*)\n+\t\t\t__gitcomp \"$(__git_refs)\" + \"${cur#+}\"\n+\t\t\t;;\n \t\t*)\n \t\t\t__gitcomp \"$(__git_refs)\"\n \t\t\t;;\n-- \n1.5.2.2.1334.g1625\n\n\n-- \nShawn.\n"},{"id":"45725","messageId":"f5n3qj$ibg$1@sea.gmane.org","threadId":"8678","inReplyTo":"20070624234759.GO17393@spearce.org","subject":"Re: problem pushing repository","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-06-25T01:01:47Z","receivedAt":"2007-06-25T01:01:47Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Shawn O. Pearce wrote:\n\n> Heh, sure.  I wrote that \"stock\" bash completion package, but at\n> this point I largely consider it to be \"complete and stable\" and\n> therefore don't put a lot of effort into it anymore.\n\nOne thing that annoys me greatly (and I think I use newest completion)\nis that sometimes _filename_ completion gets confused on the '.' separating\nbasename and extension, and instead of completing extension it adds another\ndot to make range operator '..' and triec to complete branch name, even if\nbasename is _not_ any branch name.\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"}]}