From: MechDR <MechDR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: Tuner-1.5.1
Date: Fri, 23 Dec 2022 17:08:15 +0100 [thread overview]
Message-ID: <20221223160815.AO_MTC0__a2z7T-gFzXMy7bRZexnweA7K1ACN9lb46I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41112@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
New comment by MechDR on void-packages repository
https://github.com/void-linux/void-packages/pull/41112#issuecomment-1364075764
Comment:
@oreo639 I do appreciate the effort and the mini command tutorial you did, but I'm stuck...
`git pull --rebase upstream master`
```
error: cannot pull with rebase: You have unstaged changes.
error: please commit or stash them.
```
Now what...
next prev parent reply other threads:[~2022-12-23 16:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 16:30 [PR PATCH] Tuner template (final) MechDR
2022-12-16 13:00 ` MechDR
2022-12-17 9:39 ` oreo639
2022-12-17 9:42 ` oreo639
2022-12-17 9:42 ` oreo639
2022-12-20 13:01 ` [PR PATCH] [Updated] New package: Tuner-1.5.1 MechDR
2022-12-20 13:02 ` MechDR
2022-12-20 14:10 ` MechDR
2022-12-20 14:48 ` paper42
2022-12-20 14:48 ` paper42
2022-12-20 14:48 ` [PR REVIEW] " paper42
2022-12-20 14:48 ` paper42
2022-12-20 17:06 ` [PR PATCH] [Updated] " MechDR
2022-12-20 17:07 ` MechDR
2022-12-21 11:21 ` MechDR
2022-12-21 18:00 ` Chocimier
2022-12-21 18:21 ` oreo639
2022-12-21 18:22 ` oreo639
2022-12-21 18:23 ` oreo639
2022-12-21 18:24 ` oreo639
2022-12-21 18:25 ` oreo639
2022-12-21 18:26 ` oreo639
2022-12-23 16:01 ` [PR PATCH] [Updated] " MechDR
2022-12-23 16:04 ` MechDR
2022-12-23 16:08 ` MechDR [this message]
2022-12-23 16:59 ` paper42
2023-01-02 14:47 ` [PR REVIEW] " paper42
2023-01-12 14:59 ` MechDR
2023-01-12 15:00 ` MechDR
2023-01-12 15:01 ` MechDR
2023-01-12 15:03 ` MechDR
2023-04-13 1:51 ` github-actions
2023-04-27 1:52 ` [PR PATCH] [Closed]: " github-actions
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=20221223160815.AO_MTC0__a2z7T-gFzXMy7bRZexnweA7K1ACN9lb46I@z \
--to=mechdr@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).