Bob Proulx wrote:
> But the cgit web server was returning a proxy error. In order to
> avoid needing to debug that on the spot I proxied it over to the old
> server temporarily. That is running okay this way for the moment.
> Can debug the local native server at our leisure.
Thanks to Assaf for
Leo Famulari wrote:
> remote: Traceback (most recent call last):
> remote: File "hooks/post-receive", line 6, in
> remote: import git_multimail
> remote: ImportError: No module named git_multimail
Thank you for that report. This is the git-multimail hook. There are
several different
On Tue, Feb 07, 2017 at 02:04:30PM -0700, Bob Proulx wrote:
> I switched git dns over to the new server (again) this morning.
> Trying not to thrash the IP address for git+ssh users too often.
> Everything git core command specific looks okay for my testing.
I pushed a commit to
Paul Smith wrote:
> Bob Proulx wrote:
> > I switched git dns over to the new server (again) this morning.
> > Trying not to thrash the IP address for git+ssh users too often.
> > Everything git core command specific looks okay for my testing.
>
> I was able to use the new server without any
On Tue, 2017-02-07 at 14:04 -0700, Bob Proulx wrote:
> I switched git dns over to the new server (again) this morning.
> Trying not to thrash the IP address for git+ssh users too often.
> Everything git core command specific looks okay for my testing.
I was able to use the new server without any
I switched git dns over to the new server (again) this morning.
Trying not to thrash the IP address for git+ssh users too often.
Everything git core command specific looks okay for my testing.
Specifically the shallow checkouts using --depth 1 that were the
previous problem are working now.
But
