Re: [git-users] Re: frustrations trying to control git through apache

2013-07-11 Thread tomgracey
> One thing I was trying to make clear is that my analysis was largely > *mechanical*, using known tools to extract the information that would > direct me to the correct part of the code. It's a collection of > well-known tricks, and since I described them clearly, you can learn > them immed

Re: [git-users] URL return error doing git pull

2013-07-11 Thread William Seiti Mizuta
On Fri, Jul 12, 2013 at 12:25 AM, Oscar wrote: > Please > name which branch you want to merge on the command line and > try again (e.g. 'git pull '). > Following what git has returned, you need to tell what is the name of the repository and the branch that you want to bring. The default reposi

[git-users] URL return error doing git pull

2013-07-11 Thread Oscar
I got the following error doing git pull. How do I fix it? error: The requested URL returned error: 403 error: The requested URL returned error: 403 error: The requested URL returned error: 403 You asked me to pull without telling me which branch you want to merge with, and 'branch.master.merge' i

Re: [git-users] Re: frustrations trying to control git through apache

2013-07-11 Thread Dale R. Worley
> From: tomgra...@gmail.com > > Wow!!! Its going to take me a seriously long time to get over the sheer > brilliance (not to mention speed) of that diagnosis - really impressive! I > have to say I am so glad you helped me with this - I can safely say I would > never in a million years have reac

Re: [git-users] Re: frustrations trying to control git through apache

2013-07-11 Thread tomgracey
Hi Dale Wow!!! Its going to take me a seriously long time to get over the sheer brilliance (not to mention speed) of that diagnosis - really impressive! I have to say I am so glad you helped me with this - I can safely say I would never in a million years have reached that conclusion without yo

Re: [git-users] Re: Problem removing large files from commit

2013-07-11 Thread Larry Martell
On Thu, Jul 11, 2013 at 9:19 AM, Larry Martell wrote: > On Thu, Jul 11, 2013 at 7:47 AM, Larry Martell > wrote: >> On Thu, Jul 11, 2013 at 6:10 AM, Thomas Ferris Nicolaisen >> wrote: >>> On Wednesday, July 10, 2013 10:30:46 PM UTC+2, Larry Martell wrote: I accidentally committed some

Re: [git-users] How to show the commit history of a file

2013-07-11 Thread Konstantin Khomoutov
On Thu, 11 Jul 2013 03:24:53 -0700 (PDT) Akira Tsuchiya wrote: > I want to retrieve the commit history of a given file. > What command should I issue? > > I expect the command like below. > > D:\GitTest> git show --commit-history test.txt > > 8194aaa > c419234 > ... git log --follow --format=

Re: [git-users] Re: Problem removing large files from commit

2013-07-11 Thread Larry Martell
On Thu, Jul 11, 2013 at 7:47 AM, Larry Martell wrote: > On Thu, Jul 11, 2013 at 6:10 AM, Thomas Ferris Nicolaisen > wrote: >> On Wednesday, July 10, 2013 10:30:46 PM UTC+2, Larry Martell wrote: >>> >>> I accidentally committed some large files, and when I pushed I got: >>> >>> remote: Error code:

Re: [git-users] Re: frustrations trying to control git through apache

2013-07-11 Thread Dale R. Worley
> From: tomgra...@gmail.com [Heavily cut -- see OP for the background.] Gack! Yuck! Crufty code! Someone should be shot! Ugh, back to reality. So I look at the trace just before the error: > Below are the last few lines of the strace before it falls over: > > close(0)

Re: [git-users] Re: Problem removing large files from commit

2013-07-11 Thread Larry Martell
On Thu, Jul 11, 2013 at 6:10 AM, Thomas Ferris Nicolaisen wrote: > On Wednesday, July 10, 2013 10:30:46 PM UTC+2, Larry Martell wrote: >> >> I accidentally committed some large files, and when I pushed I got: >> >> remote: Error code: b68f56c6735645b9d397abe957c294d7 >> remote: warning: Error GH41

[git-users] Re: frustrations trying to control git through apache

2013-07-11 Thread tomgracey
Hi Dale Thanks for the thoughts - I really appreciate you looking at this. 'strace' was a great suggestion and new discovery for me. I can't say I am sure how to analyse the output yet, but at least I am able to identify which file it is trying to write to when it falls over. I made another dis

[git-users] Re: Problem removing large files from commit

2013-07-11 Thread Thomas Ferris Nicolaisen
On Wednesday, July 10, 2013 10:30:46 PM UTC+2, Larry Martell wrote: > > I accidentally committed some large files, and when I pushed I got: > > remote: Error code: b68f56c6735645b9d397abe957c294d7 > remote: warning: Error GH413: Large files detected. > remote: warning: See http://git.io/iEPt8g fo

[git-users] Re: Problem removing large files from commit

2013-07-11 Thread Thomas Ferris Nicolaisen
On Wednesday, July 10, 2013 10:30:46 PM UTC+2, Larry Martell wrote: > I accidentally committed some large files, and when I pushed I got: > > remote: Error code: b68f56c6735645b9d397abe957c294d7 > remote: warning: Error GH413: Large files detected. > remote: warning: See http://git.io/iEPt8g for m

[git-users] Re: How to show the commit history of a file

2013-07-11 Thread Thomas Ferris Nicolaisen
On Thursday, July 11, 2013 12:24:53 PM UTC+2, Akira Tsuchiya wrote: > I want to retrieve the commit history of a given file. > What command should I issue? > > This oughta do it: git log path/to/file -- You received this message because you are subscribed to the Google Groups "Git for hum

[git-users] How to show the commit history of a file

2013-07-11 Thread Akira Tsuchiya
I want to retrieve the commit history of a given file. What command should I issue? I expect the command like below. D:\GitTest> git show --commit-history test.txt 8194aaa c419234 ... -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To