Hi,
On Wed, 2020-11-11 at 17:00 +0100, Markus Elfring via evolution-hackers
wrote:
> I thought that circumstances would evolve in ways so that a
> repository like
> “https://gitlab.gnome.org/GNOME/evolution-data-server/-/tree/master/src/modules”
> would become one of the preferred installa
>> I imagined then that the module “alarm-notify” could be offered as
>> auxiliary for the service implementation.
>
> So it is, no?
I thought that circumstances would evolve in ways so that a repository like
“https://gitlab.gnome.org/GNOME/evolution-data-server/-/tree/master/src/modules”
would be
Hi,
On Wed, 2020-11-11 at 15:56 +0100, Markus Elfring via evolution-hackers
wrote:
> I imagined then that the module “alarm-notify” could be offered as
> auxiliary for the service implementation.
So it is, no?
Bye,
Milan
___
ev
> those are reasons, not opinions. They cannot be reconsidered. To be
> more specific, the module lives in Evolution, because:
> - it's Evolution's extension of the data server's code
I imagined then that the module “alarm-notify” could be offered as auxiliary
for the service implementation.
Rega
On Wed, 2020-11-11 at 14:35 +0100, Markus Elfring via evolution-hackers
wrote:
> > There are reasons why it's where it is.
>
> Can they be reconsidered occasionally?
Hi,
those are reasons, not opinions. They cannot be reconsidered. To be
more specific, the module lives in Evolution, be
>>> There are reasons why it's where it is.
>>
>> Can they be reconsidered occasionally?
>
> Not if you don't explain which problem that would solve.
We came along clarification attempts if an installation dependency
is always appropriate for the system library directory.
> As a clear explanat
On Wed, 2020-11-11 at 14:35 +0100, Markus Elfring wrote:
>
> > There are reasons why it's where it is.
>
> Can they be reconsidered occasionally?
Not if you don't explain which problem that would solve. As a clear
explanation. With a use case. Explaining what you are trying to do.
Not as yet ano
> * the "alarm-notify" module is the one in Evolution, right?
Yes.
> It's not said anywhere.
I mentioned a bit of information which indicate that you changed something.
> That you reference a commit doesn't mean everybody will thoroughly read it
> to figure out what you really want.
It
On Wed, 2020-11-11 at 13:17 +0100, Markus Elfring via evolution-hackers
wrote:
> I propose to clarify further software development ideas according to
> this commit:
Hi,
the thing is that it's unclear what those "ideas" are. You forgot to
introduce what you are talking about and what you wa
>> Where do the recurring understanding difficulties come from?
>
> From your communication style and unwillingness to follow guidelines,
> as explained dozens of times before.
There are several factors involved which make also our
communication approaches challenging.
> Do you enjoy asking the
On Wed, 2020-11-11 at 12:43 +0100, Markus Elfring via evolution-hackers
wrote:
> > > The component is still stored in a repository which belongs to a
> > > client program instead of the mentioned data service
> > > implementation.
> > >
> > > How do you think about to manage this module as a compan
>> The component is still stored in a repository which belongs to a
>> client program instead of the mentioned data service implementation.
>>
>> How do you think about to manage this module as a companion component
>> in the service repository?
…
> Before you fill a new ticket, could you rephrase
On Wed, 2020-11-11 at 09:50 +0100, Markus Elfring via evolution-hackers
wrote:
> The component is still stored in a repository which belongs to a
> client program instead of the mentioned data service implementation.
>
> How do you think about to manage this module as a companion component
> in th
Hello,
A commit subject for a known software component contains the information
“Move evolution-alarm-notify to evolution-data-server”.
2018-05-11:
https://gitlab.gnome.org/GNOME/evolution/-/commit/499518d53c7e7c64bed3c58680edba49be477a4e
The component is still stored in a repository which belong
14 matches
Mail list logo
