Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Elaborate on xbump usage; advise browsing srcpkgs for examples.
Date: Wed, 06 Nov 2019 12:51:23 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16181@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 410 bytes --]

There is a new pull request by flexibeast against master on the void-packages repository

https://github.com/flexibeast/void-packages modify-contributing
https://github.com/void-linux/void-packages/pull/16181

Elaborate on xbump usage; advise browsing srcpkgs for examples.
This PR is based on user feedback in #16043.

A patch file from https://github.com/void-linux/void-packages/pull/16181.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-modify-contributing-16181.patch --]
[-- Type: text/x-diff, Size: 2021 bytes --]

From 029cef757f601aba155816c9cc2c7755ea9637bb Mon Sep 17 00:00:00 2001
From: Alexis <flexibeast@gmail.com>
Date: Wed, 6 Nov 2019 22:46:49 +1100
Subject: [PATCH] Elaborate on xbump usage; advise browsing srcpkgs for
 examples.

---
 CONTRIBUTING.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 4b5a5a6ef1a..077381f784e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -21,7 +21,7 @@ as specific git- or svn-revisions anymore.
 
 templates must be placed in `void-packages/srcpkgs/<pkgname>/template` where `pkgname` is the same as the pkgname variable in the template.
 
-For deeper insights on the contents of template files consider reading the [manual](https://github.com/void-linux/void-packages/blob/master/Manual.md)
+For deeper insights on the contents of template files consider reading the [manual](https://github.com/void-linux/void-packages/blob/master/Manual.md), and be sure to browse the existing template files in the `srcpkgs` directory of this repository for concrete examples.
 
 There's a helper tool for creating new packages in the [xtools](https://github.com/chneukirchen/xtools) package:
 
@@ -46,9 +46,11 @@ If you want to describe your changes in more detail, make an empty line and add
 
 This is also described in the [manual](https://github.com/void-linux/void-packages/blob/master/Manual.md) in deeper detail.
 
-There's a helper tool for committing packages in the [xtools](https://github.com/chneukirchen/xtools) package:
+There's a helper tool for committing packages in the [xtools](https://github.com/chneukirchen/xtools) package, which can be used when adding or updating a package:
 
-    $ xbump <pkgname>
+    $ xbump <pkgname> <git commit options>
+
+`xbump` will use `git commit` to commit the changes with the appropriate commit message. For more fine-grained control over the commit, specific options can be passed to `git commit` by adding them after the package name. 
 
 ### Starting a pull request
 

             reply	other threads:[~2019-11-06 11:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 11:51 voidlinux-github [this message]
2019-11-09 20:29 ` [PR PATCH] [Merged]: " voidlinux-github

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16181@inbox.vuxu.org \
    --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).