[git-users] gitk: file name too long
Hi, I'm using git on windows 7 and lately I've been getting the following message whenever I try to refresh my gitk view: Error executing git log: couldn't execute git: file name too long After some research this issue seems to be fixed, see https://code.google.com/p/msysgit/issues/detail?id=387. So I upgraded to 1.8.5.2.mysysgit.0 but I am still getting the problem. None of my colleagues who are working with the same repository have the problem and I have already shortened the path the my clone directory. Any hints on how I could proceed trying to fix this? Thanks in advance, Tom -- 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/groups/opt_out.
Re: [git-users] gitk: file name too long
On Thu, 30 Jan 2014 02:19:55 -0800 (PST) Tom Steynen tom_s...@hotmail.com wrote: I'm using git on windows 7 and lately I've been getting the following message whenever I try to refresh my gitk view: Error executing git log: couldn't execute git: file name too long After some research this issue seems to be fixed, see https://code.google.com/p/msysgit/issues/detail?id=387. So I upgraded to 1.8.5.2.mysysgit.0 but I am still getting the problem. None of my colleagues who are working with the same repository have the problem and I have already shortened the path the my clone directory. Any hints on how I could proceed trying to fix this? Still, could you please disclose what is the full pathname of your repository and what is the pathname of the offending file in the repository? If you can't detect the offending file, you could try to infer what it is--I presume you should have been looking at that file's diff or commit log in gitk. You might consider to not post this data here but rather do the calculation yourself: the length of the name of the file in your repo must be under MAX_PATH characters which is 260 [1]. As to different behaviour of gitk between your development workstations... does the situation change if you set the knob patch / files atop of the bottom-right window to files? 1. http://msdn.microsoft.com/en-us/library/aa365247 -- 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/groups/opt_out.
Re: [git-users] gitk: file name too long
From: Tom Steynen tom_s...@hotmail.com None of my colleagues who are working with the same repository have the problem and I have already shortened the path the my clone directory. One thing I'd check is whether the name of the repository directory on my system is longer than the name on other people's systems. 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/groups/opt_out.
[git-users] Re: Unable to install Git after building _everything_
What I did to fix the problem was this: To get docbook installed: $ sudo yum -y --enablerepo=*epel* install docbook2X To git the make to work properly: $ sudo ln -s /usr/bin/db2x_docbook2texi /usr/bin/docbook2x-texi Hope that helps. Toby On Wednesday, October 17, 2012 7:19:22 AM UTC-7, Yves S. Garret wrote: Hello, I've run the following commands (which I found in INSTALL) and the error that I got is shown below the commands: Commands: $ make prefix=/usr all doc info ; $ make prefix=/usr install install-doc install-html install-info ; Error: # install RelNotes/1.7.9.txt /usr/share/doc/git-doc/RelNotes/1.7.9.txt # install RelNotes/1.8.0.txt /usr/share/doc/git-doc/RelNotes/1.8.0.txt # install docbook-xsl.css /usr/share/doc/git-doc/docbook-xsl.css make[1]: Leaving directory `/home/ashvets/git-learning/git/Documentation' make -C Documentation install-info make[1]: Entering directory `/home/ashvets/git-learning/git/Documentation' make[2]: Entering directory `/home/ashvets/git-learning/git' make[2]: `GIT-VERSION-FILE' is up to date. make[2]: Leaving directory `/home/ashvets/git-learning/git' DB2TEXI user-manual.texi /bin/sh: line 1: docbook2x-texi: command not found make[1]: *** [user-manual.texi] Error 127 make[1]: Leaving directory `/home/ashvets/git-learning/git/Documentation' make: *** [install-info] Error 2 I'm doing this in Cygwin. What's the docbook2x-texi command and how can I get it? I downloaded this source (http://sourceforge.net/projects/docbook2x/ === ./configure make make install) and got this error instead: XMLTO gitnamespaces.7 ASCIIDOC gitrevisions.xml XMLTO gitrevisions.7 ASCIIDOC gitworkflows.xml XMLTO gitworkflows.7 ASCIIDOC gitcredentials.xml XMLTO gitcredentials.7 make[1]: Leaving directory `/home/ashvets/git-learning/git/Documentation' make -C Documentation info make[1]: Entering directory `/home/ashvets/git-learning/git/Documentation' GEN doc.dep make[2]: Entering directory `/home/ashvets/git-learning/git' make[2]: `GIT-VERSION-FILE' is up to date. make[2]: Leaving directory `/home/ashvets/git-learning/git' make[1]: Leaving directory `/home/ashvets/git-learning/git/Documentation' make[1]: Entering directory `/home/ashvets/git-learning/git/Documentation' make[2]: Entering directory `/home/ashvets/git-learning/git' make[2]: `GIT-VERSION-FILE' is up to date. make[2]: Leaving directory `/home/ashvets/git-learning/git' DB2TEXI user-manual.texi /bin/sh: line 1: docbook2x-texi: command not found make[1]: *** [user-manual.texi] Error 127 make[1]: Leaving directory `/home/ashvets/git-learning/git/Documentation' make: *** [info] Error 2 Now I'm just confused... -- 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/groups/opt_out.
[git-users] Git and SVN Repo sharing possible ?
Hi All We are tasked to move a code branch named A within SVN repo to Git. We also have trunk merges going on between A and trunk in SVN. Is it possible to set up with Git and SVN such that 1) Trunk changes in SVN could be propagated to Git version control ? If not, how can we resolve this need with an efficient setup ? We don't think it is possible but we like to confirm. Thanks -- 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/groups/opt_out.
[git-users] Re: Git and SVN Repo sharing possible ?
On Thursday, January 30, 2014 10:04:30 PM UTC+1, Zk W wrote: Hi All We are tasked to move a code branch named A within SVN repo to Git. We also have trunk merges going on between A and trunk in SVN. Is it possible to set up with Git and SVN such that 1) Trunk changes in SVN could be propagated to Git version control ? If not, how can we resolve this need with an efficient setup ? What are you trying to achieve here? Why are you moving just one branch to Git? If you just want to start using Git while still keeping the project in SVN, try out git-svn. You can clone parts (like the A branch) to a Git repository, while still being able to sync with SVN. I've got a bunch of how-to's here: http://www.tfnico.com/presentations/git-and-subversion -- 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/groups/opt_out.
Re: [git-users] gitignore change for tracked / untracked files
Hello, sorry for the late answer. Am Mittwoch, 22. Januar 2014 21:27:18 UTC+1 schrieb Magnus Therning: I'm not 100% sure I understand what you wish to do, but you might want to look at `git clean`. By default it just lists the files it would delete, you have to pass it '-f' to actually remove stuff. You can also control whether you want it to deal with ignored files or not. I'm using gitignore like a black list, so my git ignore defines all files which are not allowed. If I switch this to a white list, I need a check if everything is all right. git clean works only with untracked files, but in my case I have got tracked files, which can be after the gitignore changing also ignored. Did you have got an idea, in which way I can change my gitignores, so that I do not forget some files? Phil -- 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/groups/opt_out.
[git-users] Subsequent signing of tags, is it possible?
Hi all, I'd like to sign git commits with my GPG key after they have been committed. I know that I can sign them at commit time using git -S. But, is it possible to sign a single commit afterwards? I use an IDE that doesn't support signing. So I'd like to add my signature to those commits from the command line. I also know that there is an autosign git config value, but this one scares me a bit. I'd like to sign commits proactively, not just by accident. Any advice? Cheers, Tom -- 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/groups/opt_out.
[git-users] ignore files with hard definition
Hello, can I define on my server repository, that the ignored file patterns are hard defined. My problem is, that each use can modify the gitignore, but I get with this modification files into the server repo, which should not be there, so I would like to define in the server (bare) repo files patterns, which should be never pushed into the repo. I would like to do this with a hook, check the pushed filelist and reject the push, if some filepattern is found Is this the correct way or is there a better solution? Philipp -- 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/groups/opt_out.
Re: [git-users] Subsequent signing of tags, is it possible?
On Thu, 30 Jan 2014 22:59:12 -0800 (PST) Tom Wieczorek t...@bibbu.net wrote: I'd like to sign git commits with my GPG key after they have been committed. I know that I can sign them at commit time using git -S. But, is it possible to sign a single commit afterwards? I use an IDE that doesn't support signing. So I'd like to add my signature to those commits from the command line. I also know that there is an autosign git config value, but this one scares me a bit. I'd like to sign commits proactively, not just by accident. IIRC, you can't sign a commit after it has been created because, well, it has been created already, and objects in the Git database are immutable. So, basically, I'd say you have two possibilities: * You should be able to amend the tip commit. This would essentially replace it (that's what `git amend` does). This should work for unpushed commits, and obviously only works for the tip commit (what HEAD points at). * You might attach an annotated tag to any commit you like. Annotated tags may be signed, and that's what, say, Git project does to do releases: a signed annotated tag is attached to a commit which designates a released state. Use `git tag -a` for this. I think the latter option is the most sensible. The idea is that there's no need to sign *each* commit because once you signed a tag, you authenticated the whole subgraph of commits reachable from this tag--simply because the tag references its commit by its SHA-1 name, it, in turn, reference all the objects comprising the committed state by the SHA-1 names of those objects, and its parent commits--by their SHA-1 names as well. Since we take SHA-1 names to be cryptographically strong (exploitation of a collision attack for injection of sensible malicious data into the repository is infeasible), by attaching a signed annotated tag to a commit you effectively sign all objects reachable from that one--even though they're not signed directly. Note that the Git repo even has the maintainer's public key injected into it--for easier verification; it's done like this: $ git tag gpg-key $(git hash-object -w my-gpg-pub.key) $ git push hub gpg-key -- 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/groups/opt_out.
