On Mon, Dec 03, 2012 at 05:51:51AM -0800, Philipp Kraus wrote:
> I have run some bare repos with http & https on Apache and get this errors:
> "GET /git/Simulation.git/info/refs?service=git-upload-pack HTTP/1.1" 200
> 2878 "-" "git/1.8.0"
>
Am Dienstag, 4. Dezember 2012 09:18:13 UTC+1 schrieb Konstantin Khomoutov:
>
> Your ScriptAliasMatch directive seems to match the URL mentioned in
> the failing POST request, hence I, personally, can only suspect a
> problem with configuration for the authentication, which you did not
> includ
Thanks for the thoughts. I am not part of a team in this particular
instance. And I am basically just learning git and perhaps how I,
personally, want to use it for some of my own purposes. I tend to do a
commit after each successful edit/compile/test cycle. Mainly so that I can
change my mind
I'm glad the squash merge is what you were looking for. It's true that you
should avoid rebasing public history, but if you're not working on a team,
you can rebase to your heart's content without worrying about messing
anybody up. With your workflow, it sounds like interactive rebasing might
be ve
I'm working on transitioning about 15 CVS modules to GIT repositories and I
think I've got a handle on how to translate the cvs triggers to make them
run on the git origin.
I have to create triggers that run from the bugzilla server against the git
origin server that will branch from either mai
On 30/11/2012 07:32, Brian Kotek wrote:
> error: RPC failed; result=55, HTTP code = 0
A quick Google points to
https://confluence.atlassian.com/pages/viewpage.action?pageId=301663267
suggesting that it's a problem with libcurl and a method of getting
further debug information.
http://stackoverflo
