From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: Opencoarrays-2.9.2
Date: Sun, 17 Jan 2021 11:35:04 +0100 [thread overview]
Message-ID: <20210117103504.8zmbGuEuIAwpgJM4SVe5NS5vClKzeUIa7_XTVuffKcM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27618@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
New comment by kawaiiamber on void-packages repository
https://github.com/void-linux/void-packages/pull/27618#issuecomment-761768503
Comment:
It looks like you pulled all changes from latest upstream master branch - over 700 commits! You might want to do a couple of things:
1. Add an upstream remote: `git remote add upstream https://github.com/void-linux/void-packages.git`
2. Rebase your branch against upstream master: `git pull --rebase upstream master`
3. Add a branch specifically for your template: `git checkout -b opencoarrays`, then add your template and push there: `git push origin opencoarrays`, switch this PR to merge from that branch rather than your forked master branch.
next prev parent reply other threads:[~2021-01-17 10:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 10:14 [PR PATCH] " ramos
2021-01-09 13:30 ` kawaiiamber
2021-01-09 13:30 ` kawaiiamber
2021-01-16 10:02 ` [PR PATCH] [Updated] " ramos
2021-01-16 10:12 ` [PR REVIEW] " kawaiiamber
2021-01-16 10:13 ` kawaiiamber
2021-01-16 10:18 ` kawaiiamber
2021-01-16 10:23 ` kawaiiamber
2021-01-16 10:41 ` kawaiiamber
2021-01-16 10:48 ` kawaiiamber
2021-01-16 10:59 ` kawaiiamber
2021-01-16 11:04 ` kawaiiamber
2021-01-17 9:43 ` [PR PATCH] [Updated] " ramos
2021-01-17 10:29 ` ramos
2021-01-17 10:35 ` kawaiiamber [this message]
2022-05-02 2:15 ` github-actions
2022-05-17 2:13 ` [PR PATCH] [Closed]: " github-actions
2021-01-17 21:11 [PR PATCH] New Package: OpenCoarrays-2.9.2 ramos
2022-05-02 2:16 ` 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=20210117103504.8zmbGuEuIAwpgJM4SVe5NS5vClKzeUIa7_XTVuffKcM@z \
--to=kawaiiamber@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).