Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <>
Subject: Re: pdf.js: update to 2.12.313
Date: Sun, 23 Jan 2022 23:36:52 +0100	[thread overview]
Message-ID: <20220123223652.qEFGWz9t4yr6HHqIxgUNBSQ4bdAcUguD_2XSSGPxoAY@z> (raw)
In-Reply-To: <>

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

New comment by paper42 on void-packages repository

@hechos The correct way to create PRs is not to create a fork, push to its master, create the PR, delete the fork and repeat. This way you can't update PRs because the fork was removed. Please use branches for each PR in one void-packages fork.

This PR contains 3 commits, but should contain only one and nobody is able to fix it.

  parent reply	other threads:[~2022-01-23 22:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 23:38 [PR PATCH] " hechos
2022-01-21 17:26 ` [PR PATCH] [Updated] " hechos
2022-01-21 20:11 ` hechos
2022-01-23 22:36 ` paper42 [this message]
2022-01-24  0:03 ` [PR PATCH] [Closed]: " paper42

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:

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

  git send-email \
    --in-reply-to=20220123223652.qEFGWz9t4yr6HHqIxgUNBSQ4bdAcUguD_2XSSGPxoAY@z \ \ \

* 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).