Re: [Savannah-hackers-public] savane git cannot be committed

[Tomasz Konojacki]

Hi!
I haven't got around to it, because it seems that all
reported isues are already fixed by Nico and I had no
free time to search for unreported errors. Sorry for
that.
Fortunately, it seems that now I have spare time, so
I will search for errors (and fix them), immediately
after my issues with ssh access to Savannah will be
fixed (I've mailed you).
Also, I'll try to fix that git issue, if nobody else gets on
it.

Tomasz

----------------------------------------
> Date: Tue, 1 Oct 2013 21:00:03 +0000
> From: address@hidden
> To: address@hidden
> CC: address@hidden
> Subject: RE: [Savannah-hackers-public] savane git cannot be committed
>
> [1] - 
> http://stackoverflow.com/questions/7228715/git-failed-to-push-some-refs-although-i-have-done-git-pull
>
> Thanks for the research. That looks like the same problem, but sorry,
> it's basically incomprehensible to me. I have no idea what "branches"
> they are talking about, or how to figure out what they are.
>
> Also, I certainly don't want to blindly do "git pull" on the live
> checkout since I have no idea what will change. How can that be
> determined (as in, git diff-aginst-what-will-be-pulled)?
>
> Anyway, you or anyone can log in to frontend.sv.gnu.org (as root) and do
> whatever needs to be done in /usr/src/savane to get the changes pushed.
>
> If no one can figure out how to fix it, an alternative would be to stop
> using git for this source.
>
> karl
>
> P.S. Tomasz, more importantly -- any chance of your working on the
> XSS/SQL/etc. attacks? Weren't you going to do that?                           
>