> On Feb 5, 2017, at 20:02, Bob Proulx wrote:
>
> sed-copy is a current copy of sed. ??
I created 'sed-copy' just today as a temp copy used to check few
things (like 'git fsck') and not working on the real copy.
It can be removed.
Hi,
> On Feb 3, 2017, at 21:35, Bob Proulx wrote:
>
> Jim Meyering wrote:
>> remote: fatal: Invalid revision range
>> ..eb9593760b3f866d6b1c1caf656be6e0f8abeee6
> That definitely looks like a hook message. I will look into it.
sed.git
On Fri, 2017-02-03 at 19:35 -0700, Bob Proulx wrote:
> Note that this isn't a migration problem. I pulled git back to the
> older server. So it might be a problem with the older git version on
> the older server.
I don't want to interrupt anyone's good work, but I wonder if there's a
hoped-for
Hi Assaf,
Assaf Gordon wrote:
> The savannah team is testing a new web server as part of the
> infrastructure upgrade efforts.
Thank you for continuing to drive on this. Note that I have been
continuing to use the new server with my local override and haven't
found anything of note. Now that
On Thu, Feb 02, 2017 at 12:51:47AM +, Assaf Gordon wrote:
The savannah team is testing a new web server as part of the
infrastructure upgrade efforts.
More info about what's being tested/fixed:
1.
Savannah's git repository (and PHP code) are now served from
Hello,
The savannah team is testing a new web server as part of the
infrastructure upgrade efforts.
For the next few hours (starting at 1-Feb-2017 19:45:00 EST),
savannah's website will use the new server.
We apologize for any service disruptions.
If you encounter any issues while visiting