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

Am Freitag, den 09.07.2021, 18:36 +0800 schrieb Zhu Zihao:
> Giovanni Biscuolo writes:
> 
> > 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
> 
> I'm OK with it, maybe rename it to `emacs-telega-server-next`?
> 
> But I'm not sure Guix maintainer would accept it or not.
This probably depends on how often we'd have to bump TDLib to make this
meaningful.  "Major" release sounds like a 1.0 → 2.0 version bump,
which if "unstable" telega only depended on stuff introduced e.g. in
1.1 → 1.2 sounds a little too strict.  However, if unstable telega
means tailing arbitrary TDLib commits, I'd rather avoid doing that.

There's so far no precedent to worry about such things, though, so I'd
rather push the existing patch after some testing or an altered one if
problems are detected.  I haven't gotten to testing things myself
either, but given that we are one stable telega release behind, now
sounds like a good time to start doing that.  (Please pardon the
laziness on my part – I typically do lexical work before practical one
to allow myself to work on other patches and projects as well.)

Regards,
Leo





  reply	other threads:[~2021-07-09 11:33 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
2021-07-09 10:36           ` Zhu Zihao
2021-07-09 11:27             ` Leo Prikler [this message]
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=0fb80caedd384347c57b0a0feaae0afff2861b96.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=49219@debbugs.gnu.org \
    --cc=all_but_last@163.com \
    --cc=g@xelera.eu \
    /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).