unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Michael Rohleder <mike@rohleder.de>
Cc: 41439@debbugs.gnu.org
Subject: [bug#41439] [PATCH] gnu: mediainfo: Update to 20.03.
Date: Thu, 21 May 2020 22:31:12 +0200	[thread overview]
Message-ID: <87imgpowrz.fsf@nckx> (raw)
In-Reply-To: <871rndp2cz.fsf@rohleder.de>

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

Michael,

Michael Rohleder 写道：
> Subject: [PATCH] gnu: mediainfo: Update to 20.03.

Thanks!

> * gnu/packages/video.scm (mediainfo): Update to 20.03.

When operating on multiple packages, you need to (list, both).

Are they required to be updated in lockstep?  Is there really no 
order in which we could update these as two separate commits?

If not, please add a comment noting that they need to be updated 
in tandem.  Or better yet: if you're reasonably sure that upstream 
is committed to their new versioning scheme, you can use

  (version (package-version libmediainfo))

in mediainfo to make that crystal clear.

Kind regards,

T G-R

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

  reply	other threads:[~2020-05-21 20:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 18:30 [bug#41439] [PATCH] gnu: mediainfo: Update to 20.03 Michael Rohleder
2020-05-21 20:31 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-05-21 21:51   ` Michael Rohleder
2020-05-23 14:23     ` bug#41439: " 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=87imgpowrz.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=41439@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=mike@rohleder.de \
    /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).