From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New package: textadept-10.6
Date: Sun, 13 Oct 2019 08:08:54 +0200 [thread overview]
Message-ID: <20191013060854.s9lDYksU1Hxgo0011YCzxVmE6CqN0yqmRt7pfn1Potk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15278@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
New comment by reback00 on void-packages repository
https://github.com/void-linux/void-packages/pull/15278#issuecomment-541389587
Comment:
@mobinmob Well, this seems like an uncommon issue for me. You see, I have submitted 2 PRs. One for [`lbry-desktop`](https://github.com/void-linux/void-packages/pull/15206) and one for `textadept` (this one). The problem is that 2 commits are both showing up in this PR for some reason. I have created separate branches, but still. Maybe `lbry-desktop` has not yet been merged, that's why. I'm not sure. I haven't done multiple PRs before within short period of time.
If you check the [New package: textadept-10.6](https://github.com/void-linux/void-packages/pull/15278/commits/c9009b962bff06282694431c68b928c6b40870f0) commit, it does not have any patches.
The patch is in the [New package: lbry-desktop-0.36.0](https://github.com/void-linux/void-packages/pull/15278/commits/f11ca7f8483b01e0fccd580fd5d3a18ce834bb0c) commit as it should be. But for some reason they are both showing up in the __Commits__ and __Files changed__ tabs in this page.
I was trying for [#Hacktoberfest](https://hacktoberfest.digitalocean.com/). Hence the hurry. Please let me know if I can do anything to not cause this in future.
next prev parent reply other threads:[~2019-10-13 6:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 17:48 [PR PATCH] " voidlinux-github
2019-10-12 15:45 ` voidlinux-github
2019-10-13 6:08 ` voidlinux-github
2019-10-13 6:08 ` voidlinux-github [this message]
2019-10-13 11:57 ` voidlinux-github
2019-10-13 17:05 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-13 17:05 ` voidlinux-github
2019-10-13 17:17 ` voidlinux-github
2019-10-13 17:17 ` voidlinux-github
2019-10-13 17:22 ` voidlinux-github
2019-10-15 8:08 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-15 8:08 ` voidlinux-github
2019-10-15 8:37 ` voidlinux-github
2019-10-15 8:37 ` voidlinux-github
2019-10-15 8:39 ` voidlinux-github
2019-10-15 8:39 ` voidlinux-github
2019-10-17 17:43 ` voidlinux-github
2019-10-17 17:43 ` voidlinux-github
2019-10-17 18:04 ` voidlinux-github
2019-10-17 18:04 ` voidlinux-github
2019-10-17 18:18 ` voidlinux-github
2019-10-17 18:18 ` voidlinux-github
2019-10-17 18:55 ` voidlinux-github
2019-10-17 18:55 ` voidlinux-github
2019-10-18 6:34 ` [PR PATCH] [Closed]: " voidlinux-github
2019-10-18 6:42 ` voidlinux-github
2019-10-18 6:44 ` voidlinux-github
2019-10-18 16:36 ` voidlinux-github
2019-10-19 16:33 ` voidlinux-github
2019-10-19 16:33 ` voidlinux-github
2019-10-19 16:41 ` voidlinux-github
2019-10-19 17:15 ` voidlinux-github
2019-10-19 19:01 ` New package: textadept-10.6 [Deprecated] voidlinux-github
2019-10-19 18:53 [PR PATCH] New package: textadept-10.6 voidlinux-github
2019-10-31 22:57 ` voidlinux-github
2019-11-02 7:15 ` voidlinux-github
2019-11-02 7:43 ` voidlinux-github
2019-11-04 5:55 ` voidlinux-github
2019-11-06 4:31 ` voidlinux-github
2020-05-18 20:21 ` Anachron
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=20191013060854.s9lDYksU1Hxgo0011YCzxVmE6CqN0yqmRt7pfn1Potk@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).