On Wed, Oct 19, 2016 at 2:22 PM, Lou Berger wrote:
Hello Lou,
> I think either we're talking past each other are have some other
> major disconnect.
Let me reassure you. If both of us speak not at the same time design and
concepts,this may be problematic :-)
About the
Le 20/10/2016 à 12:29, Nicolas Dichtel a écrit :
I vote to remove them also.
+1
___
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-dev
Le 20/10/2016 à 12:15, Paul Jakma a écrit :
> Oh,
>
> I'm also thinking of deleting the various round-8 intermediate proposed
> branches, that were rendered unreferenced by any other head or tag after
> rebases
> (i.e. they're not in the history of current 'master'). I don't see a need for
>
Le 20/10/2016 à 12:12, Paul Jakma a écrit :
> On Thu, 20 Oct 2016, Nicolas Dichtel wrote:
>
>> For example, a clone of the repo does not fetch by default this kind of tag.
>> You need to do 'git fetch -t'.
>
> Ok, pushed a stable/1.0 branch, with the head commit being the one pointed to
> by
>
Oh,
I'm also thinking of deleting the various round-8 intermediate proposed
branches, that were rendered unreferenced by any other head or tag after
rebases (i.e. they're not in the history of current 'master'). I don't
see a need for them now myself really. Does anyone else have a view on
On Thu, 20 Oct 2016, Nicolas Dichtel wrote:
For example, a clone of the repo does not fetch by default this kind
of tag. You need to do 'git fetch -t'.
Ok, pushed a stable/1.0 branch, with the head commit being the one
pointed to by that tag (which seems to cause the tag to be fetched as a
Le 20/10/2016 à 11:20, Paul Jakma a écrit :
> On Thu, 20 Oct 2016, Nicolas Dichtel wrote:
>
>> A naive question: is it expected that the tag of the release is not on a
>> branch?
>
> A point-release of an old release maybe could just be referenced by the tag I
> guess - not really expecting
On Thu, 20 Oct 2016, Nicolas Dichtel wrote:
A naive question: is it expected that the tag of the release is not on
a branch?
A point-release of an old release maybe could just be referenced by the
tag I guess - not really expecting more work there. Anyone feel strongly
about it needing a
Le 18/10/2016 à 16:50, Paul Jakma a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Quagga 1.1.0 has been released, available from the usual place:
>
> https://download.savannah.gnu.org/releases/quagga/
A naive question: is it expected that the tag of the release is not on a