[git-users] Re: Created yet another git tutorial
> Apparently I underestimated the reception of my article on Git workflow. > It's going to be featured in Dr. Dobb's Journal next month :D > Awesome. Congratulations :) -- 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] lots of files
i want to setup git for my entire team, tons of files, many directories, etc ... i do NOT want everyone to clone all these files to their machine, but if they make changes, i want to track them ... for example on a shared drive there are many projects, each project has many folders with different files, etc ... should i make repos for every subdirectory under the main one? what is the best way to do this? -- 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 bisect fixed/unfixed option
Dear Git expert, I wonder how adding to git bisect fixed/unfixed options. This in order to find a good patch fixing a bug and not to find the bad commit. This is helpful for me. I am working with git version 1.7.11.7 Can you please advise on how adding these commands to git bisect. Many thanks in advance. Mehdi -- 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] where/how did files disappear?
> From: Rustom Mody > 1. How did/could those files have been deleted -- as I said I am not a > developer and so have none of my own modifications? Those files could have been deleted in any way that files can be deleted. Since "git reset --hard" caused them to appear again, it's unlikely that pulling the new commits caused it. My personal guess would be that the new build system doesn't conflicts with files that were generated by the old build system. You say that you did "git pull", followed by a rebuild, but you did not say that you cleaned the build directories before the rebuild. My experience is that when a build system is reorganized, the chances are high that you need to completely clean the build directories to get the new build system to work. > 2. Is reset --hard the correct way? The correct way to do what? If you want a completely clean build environment, "git reset --hard" ensures that all tracked files match the current commit. But you need to do "git status" to see if there are any untracked file in the working directories, and then delete those files. (In your case, there were no such 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/groups/opt_out.
Re: [git-users] bash SHA-1 completion
> From: Konstantin Khomoutov > > But really let's just look at the problem: there's no single registry > of object names which would facilitate their quick lookups. So full > support of SHA-1 completions appears to be infeasible to implement. There must be some sort of index of object names, because you can look up objects by giving only their hashes. Some of the object names are the file names in .git/objects/??/*, though I haven't figured out how the "pack" files are indexed. I suspect the reason that hash completion hasn't been done yet is more that it isn't very useful. If you type "8d40fc" and auto-completion offers 8d40fc7e56eeb9ea725054822de5c8c145a65c 8d40fc088ee0223992617c6e45f0bae7915161 8d40fc0263d7cfc32017fdbf8cb9101613ab9c that won't prompt your memory, "Ah, yes, 8d40fc088ee0223992617c6e45f0bae7915161 is the one I was looking for!" In most modern systems, you use a hash only when you copy it from somewhere else, and there usually is a cut-and-paste functionality that allows you to do that. 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: Created yet another git tutorial
On Monday, July 8, 2013 1:34:46 AM UTC-4, Thomas Ferris Nicolaisen wrote: > On Monday, July 8, 2013 1:30:39 AM UTC+2, Scott Danzig wrote: > >> I was just going to outline my typical workflow with Git, but I tend to >> want to make sure the reader understands what I talk about, and figure, >> even if there are a million things on the internet, it might be my way of >> explaining it that someone groks. I ended up adding a massive Git tutorial >> section. Not comprehensive, but enough to get someone going. Wondering if >> anyone here wants to have a look at it and let me know if you think it was >> worthwhile or not? :) >> >> http://sdanzig.blogspot.com/2013/07/introduction-to-git-along-with-sensible.html >> >> Cool stuff! I like that you take very small steps with lots of > screenshots. That does separate it from other tutorials out there, so I > think it has value. You just have to make sure it's linked to from the > proper places. > You can add it here: > https://git.wiki.kernel.org/index.php/GitDocumentation > And you can also go around to other blogs about Git documentation and > mention it in a comment. I've taken the liberty of sharing it with the Git > community on Google+. > Apparently I underestimated the reception of my article on Git workflow. It's going to be featured in Dr. Dobb's Journal next month :D -- 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 submodule add failed
I want to add git submodule *$ git submodule add git+ssh://g...@bitbucket.org:userName/lib2.git node_modules/lib2* Cloning into 'node_modules/lib2'... ssh: Could not resolve hostname bitbucket.org:userName: nodename nor servname provided, or not known fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Clone of 'git+ssh://g...@bitbucket.org:userName/lib2.git' into submodule path 'node_modules/lib2' failed Allthough I can do ... git clone g...@bitbucket.org:userName/lib2.git ... without problems. So I have valid ssh keys. My os is OsX. -- 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] bash SHA-1 completion
On Mon, 8 Jul 2013 11:41:09 -0700 (PDT) Andy From wrote: > I wonder if there's been any work on providing SHA-1 tab completion > for any command (e.g. show or diff) ? > Completion works fine for e.g. branches but it might be a convenience > feature to also be able to complete on SHA-1. > > Maybe there would be some performance drawbacks on this and there's > been some discussion on this already... A question like this should be directed to the main Git list (git at vger.kernel.org, see [1]) which is dedicated to discussing of the Git development. But really let's just look at the problem: there's no single registry of object names which would facilitate their quick lookups. So full support of SHA-1 completions appears to be infeasible to implement. On the other hand, the completion function could run `git for-each-ref ...` and try to complete through the list of returned SHA-1 names of those references. That would only include SHA-1 names of all the branches, tags, notes etc but supposedly that would be okay for most practical uses. 1. http://vger.kernel.org/vger-lists.html#git -- 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.
