Re: [Texmacs-dev] Re: savannah downtime

[Gubinelli Massimiliano]

Hi Sam and all,
 as I wrote in a previous mail. It is no more necessary. Thanks for the help. 
Savannah backup is more recent than your git repository or my backup so I used 
it to commit again the last work done on trunk. I've synchronized my git 
repository at gitourious with the current svn status so you can pull from there 
the most recent revisions. 

I will try to maintain the git mirror in sync with svn.

best
max




On 30 nov. 2010, at 10:03, Sam Liddicott wrote:

> 
> On 29/11/10 21:13, Gubinelli Massimiliano wrote:
>> Great.
>>  my working tree is at rev 3875.  It is possible to automatically backport 
>> the git patches to svn?
> 
> Yes. When we confirm the restored svn head, I can produce the patches
> 
> Is there an svn batch-mode and preferred format where I can supply a load of 
> patches for an SVN admin?
> 
> Or we could just give me svn write-privs for the day and I can push directly, 
> but I'm not sure if it will put me down as the author, s it may be better to 
> use an SVN tool for that.
> 
> Sam
> 
>> max
>> 
>> PS: in any case savannah is still down. Let's hope things get fixed soon.
>> 
>> 
>> On 29 nov. 2010, at 22:09, Sam Liddicott wrote:
>> 
>>> On 29/11/10 20:47, Gubinelli Massimiliano wrote:
>>>> I have a backup copy of the svn repository up to rev 3766.
>>> I've been using git-svn so I have every trunk commit up to 3838
>>> 
>>> Sam
>>> 
>>>> best
>>>> max
>>>> 
>>>> 
>>>> 
>>>> On 29 nov. 2010, at 21:32, Gubinelli Massimiliano wrote:
>>>> 
>>>>> Hi all,
>>>>> Savannah experienced a serious downtime yesterday and today and it is 
>>>>> still down. Here the message on the web page
>>>>> 
>>>>> *Savannah is currently down - details to follow.*
>>>>> 
>>>>> There's been a SQL injection leading to leaking of encrypted passwords, 
>>>>> some of them discovered by brute-force attack, leading in turn to project 
>>>>> membership access.
>>>>> We're reinstalling the system and restoring the data from a safe backup, 
>>>>> probably November 24th.
>>>>> Please prepare to recommit your changes since that date.
>>>>> 
>>>>> No firm previsions for the return online yet.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Please keep your working copies because probably we have to reconstruct 
>>>>> the last few days of work.....
>>>>> 
>>>>> This is the second time in 2 years that this happens.
>>>>> 
>>>>> best
>>>>> max
>>>>> 
>>>> 
>>>> _______________________________________________
>>>> Texmacs-dev mailing list
>>>> address@hidden
>>>> http://lists.gnu.org/mailman/listinfo/texmacs-dev
>>> 
>>> -- 
>>> [FSF Associate Member #2325]<http://www.fsf.org/register_form?referrer=2325>
>>> 
>>> <http://www.openrightsgroup.org/>
>>> 
>>> _______________________________________________
>>> Texmacs-dev mailing list
>>> address@hidden
>>> http://lists.gnu.org/mailman/listinfo/texmacs-dev
>> 
>> _______________________________________________
>> Texmacs-dev mailing list
>> address@hidden
>> http://lists.gnu.org/mailman/listinfo/texmacs-dev
> 
> 
> -- 
> [FSF Associate Member #2325] <http://www.fsf.org/register_form?referrer=2325>
> 
> <http://www.openrightsgroup.org/>
> 
> _______________________________________________
> Texmacs-dev mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/texmacs-dev