From: anjandev <anjandev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Manual: added link to xtools' xbump
Date: Sun, 19 Apr 2020 03:19:49 +0200 [thread overview]
Message-ID: <20200419011949.lrLz3KAdICO-aiS_UWuc3TSaYerBts6-A4C45KuTqjo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21087@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
There is an updated pull request by anjandev against master on the void-packages repository
https://github.com/anjandev/void-packages manual
https://github.com/void-linux/void-packages/pull/21087
Manual: added link to xtools' xbump
A patch file from https://github.com/void-linux/void-packages/pull/21087.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-manual-21087.patch --]
[-- Type: text/x-diff, Size: 1830 bytes --]
From 01e58fda07c9ffe75ab680982ae6992bb2305358 Mon Sep 17 00:00:00 2001
From: Anjandev Momi <anjan@momi.ca>
Date: Sat, 18 Apr 2020 18:17:10 -0700
Subject: [PATCH] Manual: added link to xtools' xbump
---
Manual.md | 22 +++++++---------------
1 file changed, 7 insertions(+), 15 deletions(-)
diff --git a/Manual.md b/Manual.md
index 92b57b1b2c2..29a8ffa604f 100644
--- a/Manual.md
+++ b/Manual.md
@@ -1960,29 +1960,21 @@ otherwise the `debug` packages won't have debugging symbols.
Fork the voidlinux `void-packages` git repository on github and clone it:
- $ git clone git@github.com:<user>/void-packages.git
-
-You can now make your own commits to the `forked` repository:
-
- $ git add ...
- $ git commit ...
- $ git push ...
+ $ git clone git@github.com:<user>/void-packages.git
+
+See [CONTRIBUTING.md](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md)
+for information on how to format your commits and other tips for
+contributing.
To keep your forked repository always up to date, setup the `upstream` remote
to pull in new changes:
- $ git remote add upstream git://github.com/void-linux/void-packages.git
- $ git pull upstream master
+ $ git remote add upstream git://github.com/void-linux/void-packages.git
+ $ git pull upstream master
Once you've made changes to your `forked` repository you can submit
a github pull request; see https://help.github.com/articles/fork-a-repo for more information.
-For commit messages please use the following rules:
-
-- If you've imported a new package use `"New package: <pkgname>-<version>"`.
-- If you've updated a package use `"<pkgname>: update to <version>."`.
-- If you've removed a package use `"<pkgname>: removed ..."`.
-- If you've modified a package use `"<pkgname>: ..."`.
<a id="help"></a>
## Help
next prev parent reply other threads:[~2020-04-19 1:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 17:44 [PR PATCH] " anjandev
2020-04-17 19:39 ` Chocimier
2020-04-17 21:07 ` [PR PATCH] [Updated] " anjandev
2020-04-17 21:08 ` anjandev
2020-04-17 21:28 ` Chocimier
2020-04-17 22:05 ` [PR PATCH] [Updated] " anjandev
2020-04-19 1:11 ` anjandev
2020-04-19 1:15 ` anjandev
2020-04-19 1:16 ` anjandev
2020-04-19 1:18 ` anjandev
2020-04-19 1:18 ` anjandev
2020-04-19 1:19 ` anjandev [this message]
2020-04-20 18:43 ` Chocimier
2020-04-20 18:43 ` [PR PATCH] [Closed]: " Chocimier
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=20200419011949.lrLz3KAdICO-aiS_UWuc3TSaYerBts6-A4C45KuTqjo@z \
--to=anjandev@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).