unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrew Tropin <andrew@trop.in>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>, 53387@debbugs.gnu.org
Cc: zevlg@yandex.ru, Nicolas Goaziou <mail@nicolasgoaziou.fr>,
	avityazev@posteo.org
Subject: [bug#53387] [PATCH 0/4] Update tdlib and telega packages
Date: Mon, 28 Nov 2022 09:43:09 +0400	[thread overview]
Message-ID: <87pmd7d47m.fsf@trop.in> (raw)
In-Reply-To: <79a67632531acfefcf781bdc942b2f60c3f3619e.camel@gmail.com>

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

On 2022-11-26 13:58, Liliana Marie Prikler wrote:

> Hi Andrew,
>
> sorry for not reacting earlier.  Is this patch still "fresh and
> relevant"?  Should we aim for newer versions?
>
> Am Donnerstag, dem 27.01.2022 um 10:54 +0300 schrieb Andrew Tropin:
>> CCed: avityazev, zevlg
>> 
>> On 2022-01-22 16:14, Liliana Marie Prikler wrote:
>> 
>> > Hi Andrew, 
>> > 
>> > Am Donnerstag, dem 20.01.2022 um 14:45 +0300 schrieb Andrew Tropin:
>> > > tdlib and telega are inteded to be used from specific commits not
>> > > tags, I keep revision and commit parameters for those packages to
>> > > make it easier to update them to untagged commits in the future.
>> > > 
>> > > https://github.com/tdlib/td/issues/1790
>> > > 
>> > > Also, updated the style for arguments.
>> > It appears Telega was already updated through a different patch. 
>> > The style adjustments are still relevant, but fail to apply
>> > currently.
>> > 
>> 
>> Updated patches.
>> 
>> > 
>> > As for commit vs. tag, I've CC'd Nicolas to make a more informed
>> > decision.  I do understand your reasoning, but OTOH I disagree with
>> > Telegram's "every commit is as good as a release" stance,
>> > particularly if there's a widely used client whose releases fail in
>> > CI :)
>> 
>> I agree, tdlib rolling release seems a little strange to me and I
>> personally not in a favor of it.  I still propose to keep commit and
>> revision variables for both tdlib and telega to be able to update
>> them from time to time to a fresh version, which surely won't have a
>> release tag.
>> 
>> 
>

Hi Liliana,

version update seems outdated, emacs-telega-server and tdlib styles
updates outdated as well.

But emacs-telega and emacs-telega-contrib style updates looks relevant
and still applies.  Slightly updated the patch, applied, pushed.

-- 
Best regards,
Andrew Tropin

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

      reply	other threads:[~2022-11-28  5:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 11:45 [bug#53387] [PATCH 0/4] Update tdlib and telega packages Andrew Tropin
2022-01-22 15:14 ` Liliana Marie Prikler
2022-01-27  7:54   ` Andrew Tropin
2022-11-26 12:58     ` Liliana Marie Prikler
2022-11-28  5:43       ` Andrew Tropin [this message]

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=87pmd7d47m.fsf@trop.in \
    --to=andrew@trop.in \
    --cc=53387@debbugs.gnu.org \
    --cc=avityazev@posteo.org \
    --cc=liliana.prikler@gmail.com \
    --cc=mail@nicolasgoaziou.fr \
    --cc=zevlg@yandex.ru \
    /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).