Tomasz Konojacki wrote:
> Additionally, I'm not sure why, but origin was set to
> git://git.sv.gnu.org/administration/savane.git which doesn't seem to
> be right,
That is the anonymous read-only access path. You can clone and read
using that URL but you can't write using it. You can make patches
Since its license is LGPL2+, I suppose no special clause is needed,
according to this old submission:
https://savannah.gnu.org/task/?12788
Good research! I still agree with what I wrote before :), so I'm glad
you proceeded as usual.
Cheers,
Karl
I would like to do this and return it to the stock version, by
uninstalling zope.
By all means!!
Thanks,
karl
I wonder whether it is actually useful to push from root@frontend.
Yes, at least to me it is. Whenever I push from other places I end up
in some kind of git hell.
Beyond that, it is the only safe thing I've found to do. Like I asked
before, how you can tell what git pull will bring in?
k
On 10/05/2013 11:40 AM, Tomasz Konojacki wrote:
Additionally, I'm not sure why, but origin was set to
git://git.sv.gnu.org/administration/savane.git which doesn't seem to be right,
see [1]. So I changed it to
r...@git.sv.gnu.org:/srv/git/administration/savane.git
and now everything works as expe
Hi!
Now I can ssh without any problems, thank you!
Regarding git issue, what I did was:
git repack
Additionally, I'm not sure why, but origin was set to
git://git.sv.gnu.org/administration/savane.git which doesn't seem to be right,
see [1]. So I changed it to
r...@git.sv.gnu.org:/srv/git/admin
