unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Zhu Zihao <all_but_last@163.com>,
	Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 49219@debbugs.gnu.org
Subject: [bug#49219] Acknowledgement ([PATCH]: Update emacs-telega.)
Date: Wed, 07 Jul 2021 15:51:21 +0200	[thread overview]
Message-ID: <87zguyut9i.fsf@xelera.eu> (raw)
In-Reply-To: <86o8bsg40d.fsf@163.com>

[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]

Hello Zhu,

thank you for your work on emacs-telega!

...sorry I'm late in this discussion.

Zhu Zihao <all_but_last@163.com> writes:

> https://github.com/zevlg/telega.el/issues/297
>
> Just ask developer of telega.
>
> Seems that we'd better to let it downgrade :thinking:

for archival purposes, this is the comment [1] by Zajcev Evgeny:

--8<---------------cut here---------------start------------->8---

0.7.0XX is for stable telega from "releases" branch

0.7.XX is for bleading edge telega from "master" branch

We need a way to distinguish them, we use leading 0 right now

--8<---------------cut here---------------end--------------->8---

Also, the upstream README.md states:

--8<---------------cut here---------------start------------->8---

This project is developed on two primary branches. The 'releases' branch
is kept in compatibility with TDLib major releases. The 'master' branch
is for developmental purposes, and utilizes unstable features in TDLib.

--8<---------------cut here---------------end--------------->8---

As a general rule (AFAIU) Guix packages usually are based on stable
releases so probably we should always use <major>.<minor>.0<N> from now
on: WDYT?

In this case I'd add a comment before (version ...) to clarify this
numbering scheme, something like:

--8<---------------cut here---------------start------------->8---

(define-public emacs-telega-server
  (package
    (name "emacs-telega-server")
    ;; 0.7.0XX is for stable telega from "releases" branch
    ;; that is kept in compatibility with TDLib major releases
    (version "0.7.024")

--8<---------------cut here---------------end--------------->8---

Also, if you think it's useful in the future we could also add a
"emacs-telega-server-unstable" for testing bleading edge TDLib features.

WDYT?

I'll give your patch series a try if I find some time this week.

Thanks! Gio'


[1] https://github.com/zevlg/telega.el/issues/297#issuecomment-868992025

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  parent reply	other threads:[~2021-07-07 13:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25  5:48 [bug#49219] [PATCH]: Update emacs-telega Zhu Zihao
     [not found] ` <handler.49219.B.162460012825885.ack@debbugs.gnu.org>
2021-06-25  6:02   ` [bug#49219] Acknowledgement ([PATCH]: Update emacs-telega.) Zhu Zihao
2021-06-25  6:23     ` Leo Prikler
2021-06-25  9:31       ` Zhu Zihao
2021-06-25 10:46         ` Leo Prikler
2021-06-26 13:16       ` Zhu Zihao
2021-06-28  2:53         ` Zhu Zihao
2021-07-06  3:04           ` Zhu Zihao
2021-07-07 13:51         ` Giovanni Biscuolo [this message]
2021-07-09 10:36           ` Zhu Zihao
2021-07-09 11:27             ` Leo Prikler
2021-07-09 13:15               ` bug#49219: " Leo Prikler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zguyut9i.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=49219@debbugs.gnu.org \
    --cc=all_but_last@163.com \
    --cc=leo.prikler@student.tugraz.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).