[git-users] Re: Configuring https
On Tuesday, July 3, 2012 7:28:20 AM UTC+2, Raviraj wrote:
My git.conf looks like following
SetEnv GIT_PROJECT_ROOT /git/repos
SetEnv GIT_HTTP_EXPORT_ALL
#AliasMatch ^/git/(.*/objects/[0-9a-f]{2}/[0-9a-f]{38})$
/gitrepos/$1
#AliasMatch ^/git/(.*/objects/pack/pack-[0-9a-f]{40}.(pack|idx))$
/gitrepos/$1
ScriptAlias /git/ /usr/local/libexec/git-core/git-http-backend/
Alias /gitrepos/ /git/repos/
Directory /git/repos/
AuthName GIT Repository
AuthUserFile /etc/git-auth-file
Require valid-user
/Directory
I am not getting the authentication box webpage when i do
https://myhost/gitrepos/myrepo
Please can some one give me step-by-step configuration of smart http
protocol and configuring the browsing repos via browser.
Hi,
I'm not sure where you've put this git.conf file. You need to tell us which
how-to you have already followed, as you're not providing enough
information here on how your setup is, like Apache version, operating
system, existing configuration, etc.
Generally, you might be better off using an out-of-the-box-solution like
Gitblit
GO http://gitblit.com/ if you aren't comfortable with configuring Apache.
Otherwise, googling for git smart http apache provides a number of
resources for you:
- http://git-scm.com/2010/03/04/smart-http.html
-
http://stackoverflow.com/questions/8021167/git-debian-apache-and-smart-http
-
http://loutilities.wordpress.com/2011/08/12/setting-up-git-with-apache-smart-https-and-ldap/
-
http://brakkee.org/site/2011/08/06/git-server-setup-on-linux-using-smart-http/
--
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/-/_gho4HEdx6QJ.
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: git status long time, gitignore
On Tuesday, July 3, 2012 6:43:14 AM UTC+2, jack sparrow wrote: btw, what's the command to display the statistics like the number of objects tracked, no.of files in the repo etc ? Find number of objects with: git count-objects -v Number of files you can find using normal unix commands, like find . -type f|grep -v .git|grep -c ./ -- 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/-/qWK3vWbQs8gJ. 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: git status long time, gitignore
On Jul 3, 11:27 am, Thomas Ferris Nicolaisen tfn...@gmail.com wrote: On Tuesday, July 3, 2012 6:43:14 AM UTC+2, jack sparrow wrote: btw, what's the command to display the statistics like the number of objects tracked, no.of files in the repo etc ? Find number of objects with: git count-objects -v Number of files you can find using normal unix commands, like find . -type f|grep -v .git|grep -c ./ the following is the output of git count-objects -v does it justify the git status to take more than a minute ? count: 0 size: 0 in-pack: 261399 packs: 5 size-pack: 1060921 prune-packable: 0 btw, Thomas thanks for your continued support, its really appreciated. garbage: 0 -- 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] Re: git status long time, gitignore
Some things you can try: - Do regular work on a RAM-diskhttp://en.wikipedia.org/wiki/RAM_drive(if you have the memory to spare), but you must remember to always push to a proper disk before restarting your computer - Invest in a solid-state-drive http://lifehacker.com/ssd/, as these tend to speed up Git repository operations significantly - Split your repository into several smaller ones Oh, and run on an unencrypted disk if possible. -- 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/-/iY5xpVEE_3oJ. 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] beginner branch question
On Wednesday, June 27, 2012 7:00:23 PM UTC+5:30, Peter J Weisberg wrote: On Tuesday, June 26, 2012, Mostafa Alshrief mostafa_alshr...@yahoo.com wrote: If any of the uncommitted changes collide with files changed between branches, it will refuse to switch, and ask you to stash the changes first what do you mean by collide with files..? If A.txt on master is different from A.txt on develop, then when you switch branches Git must change A.txt on disk. If you have uncommited changes, so that A.txt on disk is different from A.txt on develop, then Git will REFUSE to switch branches if doing so would require changing A.txt. That's what was meant by a collision. However, if A.txt on master is the same as A.txt on develop, then it doesn't need to be changed when you switch branches. Git is able to switch without corrupting your local changes. -- -PJ Gehm's Corollary to Clark's Law: Any technology distinguishable from magic is insufficiently advanced. I don't understand why each branch has to be related to one another. Here's my thought, i should be able to create multiple branches each possibly with certain tag version. The work done in each branch can be on completely different files or the same files. Once changes to a branch is complete they can be commited and pushed to the master. These changes can be pulled in to the other branch by pulling the changes from the master. If there are any conflicts they can be resolved manually. This way i can work parallely on multiple things without affecting from each other. I was of this opinion when i first came to know about git branching. -- 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/-/6c8evtGAJa0J. 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 server problem
thanks a lot, in my case this happens between RHEL Win so I assume it might be similar, I'll try this option and update with results On Monday, July 2, 2012 9:22:46 PM UTC+3, Wes Freeman wrote: This happens sometimes if you have different default permissions on the files, I've found. It seemed to happen going between a mac and a windows client, for example. This might not be the same problem you're seeing, but I figured I would chime in, just in case it is of use. You can ignore changes like this on the client side with: git config core.filemode false Wes On Mon, Jul 2, 2012 at 2:15 PM, PJ Weisberg pjweisb...@gmail.com wrote: On Monday, July 2, 2012, Avner Tamir avner.ta...@hp.com wrote: ,Hi I’ve set git server on RHEL 5.6 box, running on httpd we’ve encountered the following scenario several times User A pushes to remote User B pull from remote User B sees the sources pushed by user A as to be committed in his local repository That sounds like a reasonable description of what pull does. What did you expect/want to see? -- -PJ Gehm's Corollary to Clark's Law: Any technology distinguishable from magic is insufficiently advanced. -- 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. -- 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/-/QdLeYGjY5I4J. 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 push says Everything up-to-date
I am having trouble understanding the concept of git local and remote versioning. For example I have a iPhone app in a local git rep. Initally this was my master branch. I then checked out a new branch git checkout -b update-2.0.1. Then I set git push origin update-2.0.1 to ensure that I have a seperate branch for developing this app update and when done merge it back into my master branch. Fine! Now that I am on my update-branch I want to create branches for every issue ID. So I say git checkout -b #3178 - when I now try to push this new issue-branch in my remote repository git says Everything-up-to-date. I don't see why it is not possible to push this issue branch to the remote repository? git remote -b returns origin/master origin/update-2.0.1 I would love to see a third branch origin/update-2.0.1/#3178 -- 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/-/KETcTKlnpfQJ. 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] beginner branch question
On Tuesday, July 3, 2012, jack sparrow dafs...@gmail.com wrote: I don't understand why each branch has to be related to one another. Here's my thought, i should be able to create multiple branches each possibly with certain tag version. The work done in each branch can be on completely different files or the same files. Once changes to a branch is complete they can be commited and pushed to the master. These changes can be pulled in to the other branch by pulling the changes from the master. If there are any conflicts they can be resolved manually. This way i can work parallely on multiple things without affecting from each other. I was of this opinion when i first came to know about git branching. Git isn't going to discard your uncommited changes without being told to do so, and it's not going to commit them without being told, either. You can use 'git stash' if you need a temoprary place to put your changes while you work on something else. -- -PJ Gehm's Corollary to Clark's Law: Any technology distinguishable from magic is insufficiently advanced. -- 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.
