From: Jari Aalto <jari.aalto@cante.net>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] yasm -- a complete rewrite of the NASM assembler
Date: Mon, 08 Oct 2012 20:14:00 -0000 [thread overview]
Message-ID: <871uh8g1r2.fsf@picasso.cante.net> (raw)
In-Reply-To: <50731E8A.8020504@tiscali.co.uk> (David Stacey's message of "Mon, 08 Oct 2012 19:42:18 +0100")
On 2012-10-08 19:42, David Stacey wrote:
| On 08/10/12 10:23, Jari Aalto wrote:
| >On 2012-10-07 22:01, David Stacey wrote:
| >|
| >| yasm...
| >
| >Builds ok, GTG. It would be nice to also to have manual pages[*] for
| >all binaries. These don't have one:
| >
| > usr/bin/vsyasm.exe
| > usr/bin/ytasm.exe
| >
| >Jari
| >
| >[*] FYI Debian includes manual pages for those and they are freely
| >dstributable. http://packages.debian.org/unstable/yasm
|
| The man page is extremely minimalistic...
However minimalistic, everyone want's to access help with:
man <command>
| ...if he would submit it to
| the yasm developers. Then all distributions of yasm would benefit.
He may already have. But waiting upstream may not always be the best
strategy for users[1]
You could also ping upstream. The more contacts, the merrier.
I would just copy the pages from Debian and in a dark, rainy autum
day, nothing else to do, improve them together.
Jari
[1] Given yasm's track record for releases, progress is slow.
The same Debian developer has maintained the package since 2006, so he
may have been in contact already.
http://packages.qa.debian.org/y/yasm.html
next prev parent reply other threads:[~2012-10-08 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 21:01 David Stacey
2012-10-08 9:23 ` Jari Aalto
2012-10-08 18:42 ` David Stacey
2012-10-08 20:14 ` Jari Aalto [this message]
2012-10-08 21:08 ` David Stacey
2012-10-09 20:48 ` David Stacey
2012-10-11 22:32 ` [RFU] " David Stacey
2012-10-11 23:44 ` Christopher Faylor
2012-10-12 9:04 ` Corinna Vinschen
2012-11-05 19:04 ` David Stacey
2012-11-05 19:39 ` Christopher Faylor
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=871uh8g1r2.fsf@picasso.cante.net \
--to=jari.aalto@cante.net \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).