From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Add Write from Stylus Labs
Date: Wed, 02 Sep 2020 19:00:04 +0200 [thread overview]
Message-ID: <20200902170004.e5jjalQsK2LKl5d3pCBXma4HSMOev_rtpETRTE2iIx0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24555@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/24555#issuecomment-685868759
Comment:
What you need to do is, assuming the `void-linux/void-packages` remote is called `upstream` in your repo,
```
git pull --rebase upstream master
git rebase -i upstream/master
```
If you are working from your fork alone, you should first do
```
git remote add upstream https://github.com/void-linux/void-packages
```
Then, in the editor that `git rebase -i` opens up, change the `pick` on the first line to `r` for `reword`, and change the `pick` on every subsequent line to `f` for `fixup. When you save and quit your editor, it will open a new editor and allow you to set a message for the first commit; give this the expected "new package" message. Every other commit in your branch will be folded into the first one, so you will reduce this PR to a single commit with the correct message.
next prev parent reply other threads:[~2020-09-02 17:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 19:58 [PR PATCH] " cat-marin
2020-08-30 21:01 ` [PR PATCH] [Updated] " cat-marin
2020-08-31 1:34 ` fosslinux
2020-08-31 2:05 ` cat-marin
2020-08-31 2:50 ` fosslinux
2020-08-31 3:28 ` [PR PATCH] [Updated] " cat-marin
2020-08-31 3:29 ` cat-marin
2020-08-31 3:58 ` [PR REVIEW] " fosslinux
2020-08-31 3:58 ` fosslinux
2020-08-31 4:23 ` [PR PATCH] [Updated] " cat-marin
2020-08-31 4:26 ` cat-marin
2020-08-31 4:27 ` cat-marin
2020-08-31 4:29 ` [PR PATCH] [Updated] " cat-marin
2020-08-31 6:15 ` fosslinux
2020-08-31 6:23 ` cat-marin
2020-08-31 6:24 ` fosslinux
2020-09-02 17:00 ` ahesford [this message]
2020-09-02 23:37 ` ahesford
2020-09-02 23:56 ` [PR REVIEW] " ahesford
2020-09-02 23:56 ` ahesford
2020-09-03 19:49 ` cat-marin
2020-09-03 19:52 ` cat-marin
2020-09-03 20:01 ` ericonr
2020-09-03 20:01 ` ericonr
2020-09-03 20:11 ` cat-marin
2020-09-03 20:12 ` [PR PATCH] [Closed]: " cat-marin
2020-09-03 20:12 ` cat-marin
2020-09-04 0:23 ` [PR REVIEW] " sgn
2020-09-04 0:25 ` sgn
2020-09-04 20:39 ` cat-marin
2020-09-05 0:18 ` fosslinux
2020-09-05 0:59 ` sgn
2020-09-05 4:36 ` cat-marin
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=20200902170004.e5jjalQsK2LKl5d3pCBXma4HSMOev_rtpETRTE2iIx0@z \
--to=ahesford@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).