On Tue, Jun 11, 2019, at 11:09 AM, Mark Sapiro wrote:
> On 6/11/19 10:35 AM, Aaryan Bhagat wrote:
> > Well I generally obtained the URL from search which somehow landed me to a
> > previous release, although this problem is not reproducible now in my
> > browser and I am at the latest release
On 6/11/19 10:35 AM, Aaryan Bhagat wrote:
> Well I generally obtained the URL from search which somehow landed me to a
> previous release, although this problem is not reproducible now in my
> browser and I am at the latest release always
So it seems the issue is you went to some URL for the
On Tue, Jun 11, 2019, at 10:54 AM, Mark Sapiro wrote:
> On 6/11/19 10:38 AM, Aaryan Bhagat wrote:
> >
> > But even when doing through mailmanclient bindings which are appropriate
> > for Postorious, it would not technically bypass creating the "User" entity
> > as the entity will be created
On Tue, Jun 11, 2019, at 8:42 AM, ariessa.norra...@gmail.com wrote:
> Hello everyone,
>
> What is the preferred style for the documentation? I noticed that in
> some part of the documentation, there exists contractions and the
> documentation is written informally.
>
> Is there a template or
On Tue, Jun 11, 2019, at 10:35 AM, Aaryan Bhagat wrote:
> Well I generally obtained the URL from search which somehow landed me
> to a previous release, although this problem is not reproducible now
> in my browser and I am at the latest release always
I can't reproduce the problem either, but
On 6/11/19 10:38 AM, Aaryan Bhagat wrote:
>
> But even when doing through mailmanclient bindings which are appropriate for
> Postorious, it would not technically bypass creating the "User" entity as the
> entity will be created when the account on postorious will be created, or am
> I missing
On Tue, Jun 11, 2019, at 10:39 AM, Aaryan Bhagat wrote:
> >mailmanclient is completely separate from Mailman core. It provides a
> >set of Python bindings that are used by Postorius and HyperKitty to
> >communicate with core via core's REST API. Its mailing list subscribe
> >method is not
>mailmanclient is completely separate from Mailman core. It provides a
>set of Python bindings that are used by Postorius and HyperKitty to
>communicate with core via core's REST API. Its mailing list subscribe
>method is not core's subscribe method and its arguments are those
>appropriate for
Well I generally obtained the URL from search which somehow landed me to a
previous release, although this problem is not reproducible now in my browser
and I am at the latest release always
___
Mailman-Developers mailing list --
On 6/10/19 11:21 PM, Aaryan Bhagat wrote:
> Upon searching more regarding various models in the Gnu Mailman, I learned
> that technically first a "User" entity is created and then a "Member" entity
> can be created in correspondence to a "Mailing-List" entity. For example
>> harry_member =
Hi Ariessa,
May I know what do you mean by a documentation guideline? And what part of
the doc is informal?
Also, for different kind of audience, the style might differ.
Yours truly,
Xiaoxing Ye
On Tue, Jun 11, 2019 at 11:43 PM wrote:
> Hello everyone,
>
> What is the preferred style for
Hello everyone,
What is the preferred style for the documentation? I noticed that in some part
of the documentation, there exists contractions and the documentation is
written informally.
Is there a template or specific guidelines for writing documentation? If not,
can I propose a new
On 6/11/19 12:56 AM, Aaryan Bhagat wrote:
> Yes, you are right this problem is not there in release 3.1 although I wonder
> why the previous release of ReadTheDocs was used by my browser as default.
At what URL did you start?
--
Mark Sapiro The highway is for gamblers,
San Francisco
[...]
> I think this is perfectly fine and I don't see much benefit in combining
> the CSS and JS files at build-time. It would allow to drop the
> django-compressor dependency but with the cost of more heavy build-time
> adjustments that need to be maintained in future.
I agree, the extra gain
Yes, you are right this problem is not there in release 3.1 although I wonder
why the previous release of ReadTheDocs was used by my browser as default.
Thanks for helping
___
Mailman-Developers mailing list -- mailman-developers@python.org
To
I have reproduced this problem - but please be aware that you are using an
old version of document. The "release-3.0" points to the old version. You
might switch to the latest version using the switch in the bottom corner of
the left.
This must be a problem of RTDs side.
Yours truly,
Xiaoxing Ye
Upon searching more regarding various models in the Gnu Mailman, I learned that
technically first a "User" entity is created and then a "Member" entity can be
created in correspondence to a "Mailing-List" entity. For example
>harry_member = mlist.subscribe(harry_user)
This, however, is totally
17 matches
Mail list logo
