Re: RFC: time for a new mingwrt/w32api release?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 16/05/16 16:14, Keith Marshall wrote:
>> On the other hand, there is a good chance that the number of 
>> affected people, actively tracking the "5.0-dev" branch, is 
>> actually zero.
> 
> That's a metric I hope we might be able to establish, at least as
> it relates to participants on this list.  I'd like to think that it
> *is* zero, since there seems to be no actual head branching from
> that label; it appears to be no more than a place holder,
> currently referring to the same location as 4.0-rc1, (which begs
> the question: why was it designated as 5.0-dev in the first
> place?)

Given that the branch point was named, but no actual branch was ever
created, is there any *real* justification for keeping that original
(virtual) branch ... especially since the 4.0-rc1 tag marks the self
same point?  I'm thinking we might just as well delete this spurious
branch, without bothering to

> 1) Rename the existing "5.0-dev" branch as "5.0-deferred".

since there's no deferred development sitting on that branch anyway.

Thoughts?

- -- 
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJXPIFxAAoJEMCtNsY0flo/CFgP/A8kVNuAZTsv+gHdI6QMZanU
RkIKg7Q4OKYDsvFdCGtWS/8wMcxeRD5b2PDeK3N5aKcQOZQgBArIJ5gDAwazuFg0
5cnSkeo5L3cdBVaxiFJ3tj+kKrJO0Zhox2Z86aAxfBlH37csYY2jIT735rgNMn9Z
UFTG+JIDk1Pf1oIjNob2xH8G2AcTF+xO3HVvlu76wtnoQeweluo7QsN+g9DPwjhO
8jjV2vvLC8gV62xQhw0h4YVrzsLLqCVy4M5dUEfyRJagB1xFj/lW3c5KLKCz3gRm
l3GbGpnooFWdjEXjbfM9HJQKm5R4CLyx7pnsfdzyBeiPBkuLMAqEJgS/WVoqlk7x
/Ye8EvbnwwEV5bQdoXivk7Cggt01srwQp0nZfpuCYFAc6BrhsA2gZ90/i+VxKvDH
0cx7LFWysTRz62Z8qQvqS+/DSw3j8Ff6iMDba8qeeIgS1tKdu3qNoMwA/21N0EwM
PUSsK2RD2ya7QCr6Lcd+o8/03BslShDa+Grnigqa7vJd574e3mHxj/lqhShZuApb
EOg7ORC6l3CCNzXPnTiZVUxWnYzv0romuYOdxnwyjRFyVjcZ7y8pz5zb8z2mAbF2
i4zrNnygsVtigayXKoQr3qxtbcsUVpzTmaOxeuaE7OQfgsvMz4NsyNW+BrSPD6jw
96EL7WXxBm47tOXkY+mY
=KkPQ
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j