[git-users] gitk showing tags n instead of actual tags
See attachment, $ git version git version 1.9.5.msysgit.0 I'd like to be able to see the actual tags, this didn't happen under a previous version. Any ideas? -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Namespaces, git-remote-ext and http
Hello, I'm struggling with a repository that contains some namespaces. The following basically shows what I'm trying: --8-- $ git init --bare myrepo.git Initialized empty Git repository in d:/test/myrepo.git/ $ git clone myrepo.git/ Cloning into 'myrepo'... warning: You appear to have cloned an empty repository. done. $ git clone ext::'git --namespace=project-one %s d:/test/myrepo.git' myrepo-project-one Cloning into 'myrepo-project-one'... warning: You appear to have cloned an empty repository. --8-- As you can see, this is quite fine :-) It's also no problem to place this repository on a http server: --8-- $ git clone http://server/path/to/myrepo.git tools Cloning into 'tools'... Unpacking objects: 100% (6/6), done. --8-- But why does the following go wrong? --8-- $ git clone ext::'git --namespace=project-one %s http://server/path/to/myrepo.git' mytest Cloning into 'mytest'... fatal: 'http://server/path/to/myrepo.git' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. --8-- URL checked multiple times, it's exactly the same as used in git clone http Any hints? Thanks in advance, Thomas -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Namespaces and HTTP
Hello, Im struggling with a repository that contains some namespaces. The following basically shows what Im trying: --8-- git init --bare myrepo.git Initialized empty Git repository in d:/test/myrepo.git/ git clone myrepo.git/ Cloning into myrepo... warning: You appear to have cloned an empty repository. done. git clone ext::git --namespace=project-one %s d:/test/myrepo.git myrepo-project-one Cloning into myrepo-project-one... warning: You appear to have cloned an empty repository. --8-- As you can see, this is quite fine :-) Its also no problem to place this repository on a http server: --8-- git clone http://server/path/to/myrepo.git tools Cloning into tools... Unpacking objects: 100% (6/6), done. --8-- But why does the following go wrong? --8-- git clone ext::git --namespace=project-one %s http://server/path/to/myrepo.git mytest Cloning into mytest... fatal: http://server/path/to/myrepo.git does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. --8-- URL checked multiple times, its exactly the same as used in git clone http Any hints? Thanks in advance, Thomas -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Re: Path nomenclature in Git
Hi John, On Wednesday, January 21, 2015, John McWilliam wrote: 1. I am a total beginner here and am constantly seeing referals to ~/FileName This is obviously shorthand for something but what? Is it the location of the Git program directory or perhaps my working tree. How can I define this? The ~ symbol is the tilde symbol. It is shorthand for your home directory. To get to your home directory, on UNIX, type cd. This is shorthand for change directory, and if you type cd and press return, by default it will put you into your home directory. You cannot define ~. 2. Is the use of SSH keys necessary or can this be bypassed. To date I have tried unsuccessfully to generate private and public keys using Putty? Using SSH keys can be bypassed. If you're using GitHub, for example, use the clone URL that start with HTTPS, instead of the one that start with git@github. You'll be obliged to enter your GitHub credentials for certain operations. Good luck! -- Rick Umali / Author: Learn Git in a Month of Lunches / www.manning.com/umali -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Re: git svn fails to dcommit multiple commits
On Thursday, January 22, 2015 at 2:02:26 PM UTC+1, Bicen Zhu wrote: Hi All, I have met the exactly same problem as describled at http://stackoverflow.com/questions/4238876/git-svn-fails-to-dcommit-even-after-clean-checkout But the question was asked 4 years ago, the answer was related http proxy, but i didn't set http_proxy, i use the latest git version v2.2.2 Anyone comment? Is your SVN server modifying the incoming commits somehow, as one of the commenters ask? -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Re: git svn fails to dcommit multiple commits
On Thursday, January 22, 2015 at 2:02:26 PM UTC+1, Bicen Zhu wrote: Hi All, I have met the exactly same problem as describled at http://stackoverflow.com/questions/4238876/git-svn-fails-to-dcommit-even-after-clean-checkout http://www.google.com/url?q=http%3A%2F%2Fstackoverflow.com%2Fquestions%2F4238876%2Fgit-svn-fails-to-dcommit-even-after-clean-checkoutsa=Dsntz=1usg=AFQjCNFZeYCx8e1skGoA4iCUMCB4ccXh8Q But the question was asked 4 years ago, the answer was related http proxy, but i didn't set http_proxy, Also note: The answer write-through proxying described in the answer has nothing to do with setting up http_proxy on your client side. It's about clustering several SVN servers together for distributing across networks for performance reasons, and I believe it is transparent to the end user. Are you using a large corporate SVN server which is spread across offices/countries? It could be that the administrators have set up write-through proxying without you knowing. Also note that not much has changed in git-svn the last 4 years, so problems that existed back then could still exist today. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Best practices: Derived Files
Hi Owen, The suggestion from Dale Worley is correct. There is a third case: 3) the derived files are difficult to derive without special knowledge or procedures. In which case, documentation is only sometimes the superior method. Mark, sf_x On Thu, Jan 22, 2015 at 1:19 AM, Gergely Polonkai gerg...@polonkai.eu wrote: Hello, the fact you are speaking about a gh-pages branch makes me assume you are working on a GitHub Page[1]. In this case yes, you must put the minified file in the repository, as GitHub won't minify it for you. Think of the gh-pages branch as the deployment area, which is coincidentally in the same Git repository, although on a separate branch. This, however, also means that you should not put the original file on the gh-pages branch, as it has nothing to do with the live environment. Best, Gergely [1] https://pages.github.com On 22 Jan 2015 05:16, Dale R. Worley wor...@alum.mit.edu wrote: Owen Densmore o...@backspaces.net writes: What's the best practice for derived files in a git repo? Don't put them in the repository. There are only two cases: (1) The version of the derived file in the repo is correct relative the files that it's derived from. In that case, the derived file is redundant. (2) The version of the derived file in the repo is *not* correct relative the files that it's derived from. In that case, the derived file is dangerous. If you deploy something from a repository, it's best to have a separate repository (or perhaps branch) whose commits are created automagically by a build process from the commits of a source repository, and contain only the files that need to be deployed. You *don't* want to have the software developers responsible for keeping derived files in a source repo synchronized with source files. Dale -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Re: git svn fails to dcommit multiple commits
Hi Thomas, Thanks for the reply, Are you using a large corporate SVN server which is spread across offices/countries? Yes, right. Maybe I should try the patch showed on the original question. On Friday, January 23, 2015 at 5:27:02 PM UTC+8, Thomas Ferris Nicolaisen wrote: On Thursday, January 22, 2015 at 2:02:26 PM UTC+1, Bicen Zhu wrote: Hi All, I have met the exactly same problem as describled at http://stackoverflow.com/questions/4238876/git-svn-fails-to-dcommit-even-after-clean-checkout http://www.google.com/url?q=http%3A%2F%2Fstackoverflow.com%2Fquestions%2F4238876%2Fgit-svn-fails-to-dcommit-even-after-clean-checkoutsa=Dsntz=1usg=AFQjCNFZeYCx8e1skGoA4iCUMCB4ccXh8Q But the question was asked 4 years ago, the answer was related http proxy, but i didn't set http_proxy, Also note: The answer write-through proxying described in the answer has nothing to do with setting up http_proxy on your client side. It's about clustering several SVN servers together for distributing across networks for performance reasons, and I believe it is transparent to the end user. Are you using a large corporate SVN server which is spread across offices/countries? It could be that the administrators have set up write-through proxying without you knowing. Also note that not much has changed in git-svn the last 4 years, so problems that existed back then could still exist today. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
