Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: aspell-el added
Date: Mon, 04 Nov 2019 15:43:22 +0100	[thread overview]
Message-ID: <20191104144322.J1w06TRAUNhxv9rSkXxCFqfoqcyeM6flJ2bfIMbHoAk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16043@inbox.vuxu.org>

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

New comment by nereusx on void-packages repository

https://github.com/void-linux/void-packages/pull/16043#issuecomment-549385333

Comment:
@flexibeast:
That is in your `contributing`: "There's a helper tool for committing packages in the xtools package: xbump"

About xbump "manual":
xbump pkgname [git commit options] – Git commit a version bump
Is it supposed to I understand it? Probably if I didn't stopped at "lower" degree in english.

Guys the most people does not know even how the mouse works. Every author of documentation has to keep this in his mind. Of course he dont need to explain the mouse, but asking to read a manual that is bad even for those who wrote, isnt good. Just mention what commands needed and how to use them... then you can add a link to original man page...

Back in smallbasic project, sourceforge had al ready did tickets and forums, but no, no one used (except 2-3 ppl). The reason it wasn;t attractive to visitors and users to involve, so I just add a phpBB forum, and wow was filled with ppl in 1-2 months commenting, asking and exchange scripts.

@the-maldridge:
I am sure there are plenty examples in srcpkgs... but someone has to point me instead of losing my time discovering a boring matter as a packager.
I have more important thinks to do, for example like patching the last grief version for linux, actually I did it yesterday for void-linux and I have problems to find, like what happend to /usr/include/ncurses/ and /usr/include/ncursesw.h... the previous time I was patched grief it was for slackware and slackware is very respecting to standard ways..


  parent reply	other threads:[~2019-11-04 14:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02  1:13 [PR PATCH] " voidlinux-github
2019-11-02  4:15 ` voidlinux-github
2019-11-02 14:05 ` voidlinux-github
2019-11-02 14:05 ` [PR PATCH] [Closed]: " voidlinux-github
2019-11-02 23:01 ` voidlinux-github
2019-11-03  4:28 ` voidlinux-github
2019-11-03 15:16 ` voidlinux-github
2019-11-03 22:41 ` voidlinux-github
2019-11-04  0:30 ` voidlinux-github
2019-11-04 14:43 ` voidlinux-github [this message]
2019-11-05  6:05 ` voidlinux-github
2019-11-05  8:04 ` 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=20191104144322.J1w06TRAUNhxv9rSkXxCFqfoqcyeM6flJ2bfIMbHoAk@z \
    --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).