From: "Ludovic Courtès" <ludo@gnu.org>
To: Raghav Gururajan <rg@raghavgururajan.name>
Cc: 48083@debbugs.gnu.org
Subject: [bug#48083] [PATCH 0/0]: Changes to Telegram Stuff
Date: Fri, 14 May 2021 12:32:12 +0200 [thread overview]
Message-ID: <87mtsxobbn.fsf_-_@gnu.org> (raw)
In-Reply-To: <20210428165141.27183-2-rg@raghavgururajan.name> (Raghav Gururajan's message of "Wed, 28 Apr 2021 12:51:40 -0400")
Raghav Gururajan <rg@raghavgururajan.name> skribis:
> * gnu/packages/telegram.scm (webrtc-for-telegram-desktop)[version]: Update
> to 0-96.18cb4cd.
> ---
> gnu/packages/telegram.scm | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/gnu/packages/telegram.scm b/gnu/packages/telegram.scm
> index cf5c173973..42e9adc7dd 100644
> --- a/gnu/packages/telegram.scm
> +++ b/gnu/packages/telegram.scm
> @@ -70,8 +70,8 @@
> #:use-module (guix build-system qt))
>
> (define-public webrtc-for-telegram-desktop
> - (let ((commit "a19877363082da634a3c851a4698376504d2eaee")
> - (revision "83"))
> + (let ((commit "18cb4cd9bb4c2f5f5f5e760ec808f74c302bc1bf")
> + (revision "96"))
Could you explain how you chose this commit?
Normally we only provide upstream releases, unless there’s a good reason
to provide a snapshot. Perhaps you could add a comment above the commit
ID explaining why we’re not using a release?
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-05-14 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 16:50 [bug#48083] [PATCH 0/0]: Changes to Telegram Stuff Raghav Gururajan via Guix-patches via
2021-04-28 16:51 ` [bug#48083] [PATCH 1/3] gnu: webrtc-for-telegram-desktop: Use usrsctp from guix instead of from third-party Raghav Gururajan via Guix-patches via
2021-04-28 16:51 ` [bug#48083] [PATCH 2/3] gnu: webrtc-for-telegram-desktop: Update to 0-96.18cb4cd Raghav Gururajan via Guix-patches via
2021-05-14 10:32 ` Ludovic Courtès [this message]
2021-04-28 16:51 ` [bug#48083] [PATCH 3/3] gnu: telegram-desktop: Update to 2.7.3 Raghav Gururajan via Guix-patches via
2021-05-14 10:33 ` [bug#48083] [PATCH 0/0]: Changes to Telegram Stuff Ludovic Courtès
2021-05-14 10:30 ` Ludovic Courtès
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=87mtsxobbn.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=48083@debbugs.gnu.org \
--cc=rg@raghavgururajan.name \
/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).