Github messages for voidlinux
 help / color / mirror / Atom feed
From: the-cleaner-66 <the-cleaner-66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update template
Date: Sat, 12 Sep 2020 06:42:32 +0200	[thread overview]
Message-ID: <20200912044232.gtyi6Qdt4yQxzkPdwN0praR50ZAnvA03OWkbp9ubAqo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24840@inbox.vuxu.org>

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

New comment by the-cleaner-66 on void-packages repository

https://github.com/void-linux/void-packages/pull/24840#issuecomment-691407721

Comment:
Thank you for the hints!
I have one question: Where do I have to place the [ci skip] flag?
Building the package took almost 60 minutes on my workstation laptop.

Kind regards
Michael Krahl

Am Fri, 11 Sep 2020 15:01:45 -0700
schrieb John Zimmermann <notifications@github.com>:

> @Johnnynator requested changes on this pull request.
> 
> Use commit naming as outlined in
> https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md
> 
> >  wrksrc="VirtualBox-${version%*a}"
>  short_desc="General-purpose full virtualizer for x86 hardware"
>  maintainer="Orphaned <orphan@voidlinux.org>"
>  license="GPL-2.0-only, CDDL-1.0"
>  homepage="https://www.virtualbox.org"
>  changelog="https://www.virtualbox.org/wiki/Changelog"
> -distfiles="http://download.virtualbox.org/virtualbox/${version%*a}/VirtualBox-$version.tar.bz2"
> -checksum=91fa05bcfce36316ca93e3927c9550ea66286fff4c5bec900b753fca278ce1a0
> +distfiles="http://download.virtualbox.org/virtualbox/${version%*a}/VirtualBox-6.1.14a.tar.bz2"
> 
> Stay with $version and just append the `a` to the version string. And
> don't bump the revision.
> 


-- 
Michael Krahl
Weiherstraße 16
D-89257 Illertissen
Tel.: 07303-43726


  parent reply	other threads:[~2020-09-12  4:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 21:57 [PR PATCH] " the-cleaner-66
2020-09-11 22:01 ` [PR REVIEW] " Johnnynator
2020-09-11 22:40 ` the-cleaner-66
2020-09-11 22:40 ` the-cleaner-66
2020-09-11 23:49 ` fosslinux
2020-09-12  0:15 ` ericonr
2020-09-12  4:42 ` the-cleaner-66 [this message]
2020-09-12  4:44 ` the-cleaner-66
2020-09-12  5:03 ` [PR REVIEW] " the-cleaner-66
2020-09-12  7:55 ` pullmoll
2020-09-12  8:08 ` [PR PATCH] [Closed]: " pullmoll
  -- strict thread matches above, loose matches on Subject: below --
2021-12-14  1:28 [PR PATCH] " zen0bit
2021-12-14 13:19 ` Duncaen
2022-01-14 12:19 ` paper42
2022-01-14 18:48 ` zen0bit
2022-01-14 22:05 ` paper42
2022-01-30 15:26 ` zen0bit
2022-01-30 17:02 ` paper42
2022-01-30 17:41 ` zen0bit
2022-01-30 17:41 ` paper42
2021-05-04 19:00 [PR PATCH] " asymmetros
2021-05-04 19:06 ` q66
2021-04-28 22:08 [PR PATCH] " grim-cypher
2021-04-28 22:52 ` ericonr
2021-04-29  0:40 ` FollieHiyuki
2021-04-29 14:46 ` ericonr
2021-05-17  3:57 ` ericonr
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20137@inbox.vuxu.org>
2020-03-16 15:37 ` Piraty

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

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

  git send-email \
    --in-reply-to=20200912044232.gtyi6Qdt4yQxzkPdwN0praR50ZAnvA03OWkbp9ubAqo@z \
    --to=the-cleaner-66@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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.
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 NNTP newsgroup(s).