Bug#913627: [pkg-uWSGI-devel] Bug#913627: Query: mountpoints and uwsgi 2.1

2021-01-09 Thread Jonas Smedegaard
This bugreport is closed as not really a bugreport (just speculations 
around upstream development).

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature


Bug#913627: [pkg-uWSGI-devel] Bug#913627: Query: mountpoints and uwsgi 2.1

2018-11-13 Thread Dean Hamstead

Ok thanks for a quick response.

The absence of much response in their GH bugs makes me wonder if unbit 
people are looking or not


Some PR seem to be actioned but thats about it


On Tue, 13 Nov 2018 10:40:04 +0100 Jonas Smedegaard  wrote:

> Quoting Dean Hamstead (2018-11-13 09:15:19)
> > I posted this here https://github.com/unbit/uwsgi/issues/1895 but
> > didnt get a response. I wonder if debian maintainers know whats
> > happening?
> >
> > According to this documentation mountpoints will be available in uwsgi
> > 2.1 (see
> > https://uwsgi-docs.readthedocs.io/en/latest/SubscriptionServer.html)
> >
> > The 2.1 milestone appears to have been met but there is no 2.1 tagged
> > release.
> >
> > I am curious if this feature will find its way in to 2.0.x releases or
> > if 2.1 has a future?
>
> Sorry, I have no special knowledge about uWSGI development.
>
> My guess is that 2.1 is the development branch, and as such it won't
> ever get "released" but instead features from there will get
> cherry-picked into the 2.0 branch.
>
> But that's just a guess...
>
>
> - Jonas
>
> --
> * Jonas Smedegaard - idealist & Internet-arkitekt
> * Tlf.: +45 40843136 Website: http://dr.jones.dk/
>
> [x] quote me freely [ ] ask before reusing [ ] keep private



Bug#913627: [pkg-uWSGI-devel] Bug#913627: Query: mountpoints and uwsgi 2.1

2018-11-13 Thread Jonas Smedegaard
Quoting Dean Hamstead (2018-11-13 09:15:19)
> I posted this here https://github.com/unbit/uwsgi/issues/1895 but 
> didnt get a response. I wonder if debian maintainers know whats 
> happening?
> 
> According to this documentation mountpoints will be available in uwsgi 
> 2.1 (see 
> https://uwsgi-docs.readthedocs.io/en/latest/SubscriptionServer.html)
> 
> The 2.1 milestone appears to have been met but there is no 2.1 tagged 
> release.
> 
> I am curious if this feature will find its way in to 2.0.x releases or 
> if 2.1 has a future?

Sorry, I have no special knowledge about uWSGI development.

My guess is that 2.1 is the development branch, and as such it won't 
ever get "released" but instead features from there will get 
cherry-picked into the 2.0 branch.

But that's just a guess...


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#913627: Query: mountpoints and uwsgi 2.1

2018-11-13 Thread Dean Hamstead
Source: uwsgi
Severity: wishlist

Dear Maintainer,

I posted this here https://github.com/unbit/uwsgi/issues/1895 but didnt
get a response. I wonder if debian maintainers know whats happening?

According to this documentation mountpoints will be available in uwsgi 2.1 (see 
https://uwsgi-docs.readthedocs.io/en/latest/SubscriptionServer.html)

The 2.1 milestone appears to have been met but there is no 2.1 tagged release.

I am curious if this feature will find its way in to 2.0.x releases or if 2.1 
has a future?

thanks


Dean


Psst! It's possible that this email contains information that is on the super 
secret side of confidential. So if you received it accidentally, let the sender 
know straight away and delete it (and the email you sent them). Also, we should 
let you know that any emails that come and go through Winc™ might be 
scanned, stored or read by Winc™ at its discretion. If you've got a 
question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 
7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it 
sends, but we can't promise that it will be error free. So, please don't hold 
it against us.