[git-users] Re: Git Http Error

2012-08-21 Thread Mavin Martin 
You're absolutely right, I checked the server and it looks like it is 
loosing authentication accessibility before its done causing the errors.  I 
found this site:

http://maymay.net/blog/2008/08/08/how-to-use-http-basic-authentication-with-git/

and it says I should make a .netrc on the Client Side.  This might fix the 
issue, the only thing is that it still prompts for a username and password. 
 Do you know much about .netrc?

This is what I wrote down:

machine [I tried both client_address.com and server_address.com]

username mavin

password [my password]


When I do a git clone, it still asks for a username and password on my Mac 
Client.  Am I setting it up correctly?

On Monday, August 20, 2012 6:37:07 PM UTC-6, Mavin Martin wrote:
>
> Hi List,
>
>
> I just installed and setup a git-scm system on one of our Ubuntu Servers. 
>  At first, everything was working fine but now I'm having issues I can't 
> fix.  Having two clients, *Client A* and *Client B*, this is what I did:
>
>
> *Server*
>
> $ git fsck
>
> $ git gc
>
>
> *Client A*
>
> $ git push
>
> Fetching remote heads...
>
>   refs/
>
>   refs/tags/
>
>   refs/heads/
>
> updating 'refs/heads/master'
>
>   from 
>
>   to   d88c184835085e5a76b58fd7cb6f96e37d6821ca
>
> sending 12 objects
>
> done
>
> Updating remote server info
>
> To https://mav...@mysite.com/git/mavin-repo/mavin-repo.git
>
>dfe89e2..d88c184  master -> master
>
>
> *Client B*
>
> $ git pull --rebase
>
> error: The requested URL returned error: 401 (curl_result = 22, http_code 
> = 401, sha1 = 4b19e6f290edb6c97bab732c5f3972df5d385319)
>
> error: Unable to find 4b19e6f290edb6c97bab732c5f3972df5d385319 under 
> https://mav...@mysite.com/git/mavin-repo/mavin-repo.git
>
> Cannot obtain needed tree 4b19e6f290edb6c97bab732c5f3972df5d385319
>
> while processing commit 61ae663334202efcee96bb69f3f48247e25f9dac.
>
> error: Fetch failed.
>
>
> *Server*
>
> $ git update-server-info
>
>
> *Client B*
>
> $ git pull --rebase
>
> error: The requested URL returned error: 401 (curl_result = 22, http_code 
> = 401, sha1 = 4b19e6f290edb6c97bab732c5f3972df5d385319)
>
> error: Unable to find 4b19e6f290edb6c97bab732c5f3972df5d385319 under 
> https://mav...@mysite.com/git/mavin-repo/mavin-repo.git
>
> Cannot obtain needed tree 4b19e6f290edb6c97bab732c5f3972df5d385319
>
> while processing commit 61ae663334202efcee96bb69f3f48247e25f9dac.
>
> error: Fetch failed.
>
>
> I think *git update-server-info *isn't executing properly, anyone know 
> how to fix this issue?  Or does the issue even have to do with my apache 
> linked with git update-server-info?
>
>
> Thanks,
>
> Mavin
>

-- 
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/-/R0IlzhbtCPAJ.
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 Http Error

2012-08-21 Thread Konstantin Khomoutov 
On Tue, 21 Aug 2012 16:27:48 +0400
Konstantin Khomoutov  wrote:

[...]
> HTTP status code 401 means "not authorised" [1] which (supposedly)
> means that while the web server was able to successfully verify your
> identity, the type of access performed by the Git client when fetching
> has been denied for you by certain web server settings.  Also web
> server could have denied your from accessing specific filesystem path
> etc.

Well, [1] even states that 401 is returned the first time a client
request access to a resource requiring authentication.
I'm not sure what exactly follows from this observation, just trying to
make things more clear.

[...]
> 1. http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

-- 
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.

Re: [git-users] Git Http Error

2012-08-21 Thread Konstantin Khomoutov 
On Mon, 20 Aug 2012 17:37:07 -0700 (PDT)
Mavin Martin  wrote:

[...]
> $ git pull --rebase
> 
> error: The requested URL returned error: 401 (curl_result = 22,
> http_code = 401, sha1 = 4b19e6f290edb6c97bab732c5f3972df5d385319)
[...]

HTTP status code 401 means "not authorised" [1] which (supposedly)
means that while the web server was able to successfully verify your
identity, the type of access performed by the Git client when fetching
has been denied for you by certain web server settings.  Also web
server could have denied your from accessing specific filesystem path
etc.

I would raise web server's debug level and inspect its error log after
failed fetches to see what request the Git client sends and how the web
server denies it.

1. http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

-- 
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.

Re: [git-users] misleading diff hunk-header

2012-08-21 Thread Tim Chase 
On 08/21/12 07:19, Konstantin Khomoutov wrote:
> On Mon, 20 Aug 2012 20:49:48 -0500
> Tim Chase  wrote:
>> tl;dr version: diff.{type}.xfuncname starts searching backwards in
>> from the beginning of the hunk, not the first differing line.
> 
> This list is for helping inexperienced Git user master Git itself.
> Please report any bugs to the main (devel) Git list which is
> git at vger.kernel.org
> 
> (More info is at http://vger.kernel.org/vger-lists.html#git)

I guess before reporting it as a bug, I was hoping to get
confirmation whether it was as-designed, or if it really was a bug.

But if it sounds sufficiently buggy, I'll gladly take it there.

-tkc



-- 
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.

Re: [git-users] misleading diff hunk-header

2012-08-21 Thread Konstantin Khomoutov 
On Mon, 20 Aug 2012 20:49:48 -0500
Tim Chase  wrote:

> tl;dr version: diff.{type}.xfuncname starts searching backwards in
> from the beginning of the hunk, not the first differing line.
[...]

This list is for helping inexperienced Git user master Git itself.
Please report any bugs to the main (devel) Git list which is
git at vger.kernel.org

(More info is at 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 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 Font in the Logo

2012-08-21 Thread Maciej Kołek 
http://scr.hu/0a0/xecx0
I've just found out the answer. Closed! :D

W dniu wtorek, 21 sierpnia 2012 10:51:16 UTC+2 użytkownik Maciej Kołek 
napisał:
>
> Maybe this is the wrong place to ask this question - but i would like to 
> know the Git Font, that is in the logo.
> I want to make a Git cheat sheet mug, with the text written in Polish:
>
> "Git jest Git" and all i need is the "jest" text made out of git font. 
> "Git" in common polish language means "cool, super, awesome".
> So the translation is quite like: "Git is awesome".
>
> Thanks in advance.
>
> -- 
> Maciej Kołek
> kon...@ferus.info 
> www.ferus.info
>
> 

-- 
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/-/D4BLKPRs4iIJ.
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 Font in the Logo

2012-08-21 Thread Konstantin Khomoutov 
On Tue, 21 Aug 2012 10:51:16 +0200
Maciej Kołek  wrote:

> Maybe this is the wrong place to ask this question - but i would like
> to know the Git Font, that is in the logo.
> I want to make a Git cheat sheet mug, with the text written in Polish:
> 
> "Git jest Git" and all i need is the "jest" text made out of git font.
> "Git" in common polish language means "cool, super, awesome".
> So the translation is quite like: "Git is awesome".

According to [1], the new Git logo was designed by Jason Long, who
seems to be available as [2] (this also has twitter link), [3] etc.
So I'd just try to reach that person by e-mail and ask.
It might turn out that there's no specific font and the logo text has
been sketched right away, but possibly you could then convince Jason to
create several pictures specifically for usage on mugs. ;-)

1. https://github.com/blog/1125-new-git-homepage
2. http://dribbble.com/jasonlong
3. https://github.com/jasonlong

-- 
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 Font in the Logo

2012-08-21 Thread Thomas Ferris Nicolaisen 
If you're talking about the logo used on git-scm.com:

https://github.com/github/gitscm-next/blob/master/public/images/logo.png

.. the author is Scott Chacon , so you should ask 
him.

Other fonts used on git-scm.com are noted here:

https://github.com/github/gitscm-next/blob/b4fc467b9de749ad0d3ab2397b243ac32db9a2d7/app/assets/stylesheets/variables.css.scss


On Tuesday, August 21, 2012 10:51:16 AM UTC+2, Maciej Kołek wrote:
>
> Maybe this is the wrong place to ask this question - but i would like to 
> know the Git Font, that is in the logo.
> I want to make a Git cheat sheet mug, with the text written in Polish:
>
> "Git jest Git" and all i need is the "jest" text made out of git font. 
> "Git" in common polish language means "cool, super, awesome".
> So the translation is quite like: "Git is awesome".
>
> Thanks in advance.
>
> -- 
> Maciej Kołek
> kon...@ferus.info 
> www.ferus.info
>
> 

-- 
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/-/YFsUuiIoyKEJ.
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 Font in the Logo

2012-08-21 Thread Maciej Kołek 
Maybe this is the wrong place to ask this question - but i would like to
know the Git Font, that is in the logo.
I want to make a Git cheat sheet mug, with the text written in Polish:

"Git jest Git" and all i need is the "jest" text made out of git font.
"Git" in common polish language means "cool, super, awesome".
So the translation is quite like: "Git is awesome".

Thanks in advance.

-- 
Maciej Kołek
kont...@ferus.info
www.ferus.info

-- 
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.

Re: [git-users] Re: Checkout a remote branch

2012-08-21 Thread Konstantin Khomoutov 
On Mon, Aug 20, 2012 at 03:27:39PM -0300, Gabriel Lau wrote:

> In my case I use a bare repository. It was the easiest way I've found to
> manage the projects sent to the server.
> I start a new repository as bare and set it to put the files of the
> project in a specific directory in the server.
I don't get this sentence: bare repos by definition have no workng tree
attached to them.  Do you mean you set up post-commit hooks in these
repos which do check out the files to a (detached) working tree (by
means of using GIT_DIR, GIT_WORK_TREE env. variables or so)?

> But some of those projects I want to set a second branch to test
> some things when needed and switch back to the master when I finish
> testing.
If the answer to my previous question is "yes", then you have almost no
problem at all: a bare repo differs from a non-bare repo only in that it
does not have a workng tree; it still can maintain any number of
branches (and tags) in it, commands like `git branch` do work in it, and
any branch/tag/commit can be checked out to a (detached) working
tree, and several working trees can be maintained in parallel.

So basically you should work along these steps:

1) Push your experimental branch to a remote repo:
   $ git push server mystuff:experiment

2) Log in to the server, create a directory for your experimental files,
   then do:
   $ export GIT_WORK_TREE=/path/to/that/directory
   $ export GIT_DIR=/path/to/your/bare/repo
   $ cd $GIT_WORK_TREE
   $ git checkout experiment

3) After you have verified everything works okay, delete that
   experimental branch--either from the server side, by running
   `git branch -D experiment` from within the bare repo directory,
   or from the client side by pushing nothing to that branch:
   `git push server :experiment`.

You might as well go further and wish to perform certain fixups
to your experimental while testing the code on the server; in this case
you could use the GIT_INDEX_FILE variable to point Git to a file to use
as the staging area for your experimental working tree (you still need
the above mentioned env. variables set as well).  This would allow you
to do any number of commits to fix your experimental code and then
fetch them from the client.  Read more on this topic in [1].

If checking out code to a detached working tree is not your way of work,
and my guess failed, please be very specific about your setup as it
seems not too much people here understand it (me included).  As usually,
not trying to be too formal when explaining helps considerably: a simple
example (or a few of them) formulated in simple words will do just OK.

1. http://git-scm.com/2010/04/11/environment.html

-- 
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.