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
still still not working
On Tue, Jan 24, 2017 at 2:08 PM, carl hansen
wrote:
> still not working
>
> On Sun, Jan 22, 2017 at 1:23 PM, Assaf Gordon
> wrote:
>
>> Hello Carl,
>>
>> > On 01/20/2017 03:42 AM, carl hansen wrote:
>> >> When I commit to
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
Leo Famulari wrote:
> Bob Proulx wrote:
> > Drat! This does appear to be a regression.
> >
> > In your opinion is that enough of a regression to warrent reverting
> > (once again) the git service back to the old server? Of course that
> > means another IP address change thrash for people who
On Tue, Feb 07, 2017 at 03:18:32PM -0700, Bob Proulx wrote:
> Leo Famulari wrote:
> > I bet that most of them use the unauthenticated HTTP or Git protocols
> > and are vulnerable to man-in-the-middle attacks and eavesdropping.
>
> Certainly it is vulnerable to easedropping. And to some extent
On Tue, Feb 07, 2017 at 02:29:36PM -0500, Paul Smith wrote:
> I'm not asking for _authenticated_ HTTPS support, just anonymous access
> over HTTPS. More straightforwardly, I'm looking for HTTPS as an
> alternative to our current HTTP support, not an alternative to our
> current SSH support.
I'd
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
Leo Famulari wrote:
> The advantage of HTTPS compared to SSH is that it can be used
> anonymously, without setting up a Savannah account. Currently, users who
> wish to fetch source code from Savannah using an authenticated protocol
> must create a Savannah account. This is inconvenient for casual
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
Just fyi... New security kernels were released yesterday. I
installed them. Which means reboots all around. I just now rebooted
all of the new VMs that received the new kernels. All good!
Bob
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
On Tue, Feb 7, 2017 at 8:27 AM, Assaf Gordon wrote:
> Hello Jim,
>
> On Mon, Feb 06, 2017 at 07:05:29PM -0800, Jim Meyering wrote:
>>
>> Grep is a GNU project, so its "devel" list would be on gnu.org, not on
>> "nongnu.org":
>> Is that something you can help change easily?
Hello Jim,
On Mon, Feb 06, 2017 at 07:05:29PM -0800, Jim Meyering wrote:
Grep is a GNU project, so its "devel" list would be on gnu.org, not on
"nongnu.org":
Is that something you can help change easily? E.g.,
https://lists.nongnu.org/archive/html/grep-devel/2017-02/msg2.html
(I'm not
13 matches
Mail list logo