GNU bug report logs - #13578
A new versioning scheme for automake releases, and a new branching scheme for the Git repository

Previous Next

Full log

View this message in rfc822 format

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: 13578 <at> debbugs.gnu.org, Automake List <automake <at> gnu.org>
Subject: bug#13578: [IMPORTANT] Savannah issues
Date: Mon, 25 Feb 2013 14:40:37 +0100

On 02/23/2013 07:06 PM, Stefano Lattarini wrote:
>
>>> In a couple of days, I will proceed with this "branch moving":
>>>
>>>    * branch-1.13.2 -> maint
>>>    * maint -> master
>>>    * master -> next
>>>
>> Done.
>>
> Damn, not really.  For some questionable reason, Savannah is rejecting
> my non-fast-forward push to master even if I specify '--force', and
> I cannot use the usual trick "delete the remote branch, then push the
> local one to it" trick that I typically use to work around this
> problem, since 'master' is the "current branch" of the remote
> repository, and that cannot be deleted to avoid confusing "git clone".
> 
> So *THE AUTOMAKE GIT REPOSITORY ON SAVANNAH IS CURRENTLY IN AN
> INCONSISTENT STATE* (not broken, mind you, merely inconsistent with
> our new declared policies), and should not be used until this issue
> is resolved.
> 
> I don't have time to look into this presently,
>
I had time today, so I submitted a Task in the Savannah interface:
<https://savannah.gnu.org/task/index.php?12497>

Regards,
  Stefano

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.