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: Sun, 03 Nov 2019 16:16:23 +0100	[thread overview]
Message-ID: <20191103151623.3BxIUTKdVBsKp9RibMEsCgt0ENUxhClRmOk40JLcqGc@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: 1597 bytes --]

New comment by nereusx on void-packages repository

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

Comment:
Well, it is useful, but needs work; less text more examples. You should starting with what ppl had to read already. Also add this in the must read https://github.com/iiitkottayam/first-contribution or something better. While I did already contributions on other projects like learnxiny it was simpliest, there are features and problems of git that I meet in this project since it has more traffic. You know the solutions, I ll have to search...
btw, what is xbump and where is the manual?

The Manual.md has also "missing parts" and its a bit hard to understand, for example why to use vman since I have vinstall? how to include a Makefile to original package so to do my job easy as already know, well there are more questions on this but you didn't ask.

Now, I am retired with health issues, but many years ago I was create the smallbasic mostly for PalmOS (from 2004 I retired from the project). I found cvs was more smart in simple task like add a directory without mess everything :P but that I has to say is you need a forum for each subporject (like the documentation). That worked excellent for me.

Also there is a wiki-void but link is not in the main site, why? how do you expect ppl to find this? The void site need to be rewritten with the major resources on the top. Find easy is a mesaure for sites quality you know... well at least it was.

That are my comments, I am happy with your works guys, I just comment for better results.

  parent reply	other threads:[~2019-11-03 15:16 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 ` [PR PATCH] [Closed]: " voidlinux-github
2019-11-02 14:05 ` voidlinux-github
2019-11-02 23:01 ` voidlinux-github
2019-11-03  4:28 ` voidlinux-github
2019-11-03 15:16 ` voidlinux-github [this message]
2019-11-03 22:41 ` voidlinux-github
2019-11-04  0:30 ` voidlinux-github
2019-11-04 14:43 ` voidlinux-github
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=20191103151623.3BxIUTKdVBsKp9RibMEsCgt0ENUxhClRmOk40JLcqGc@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).