ECNeilson <eric@neilsonhart.com> spake the secret code ><117cof5$tinj$1@dont-email.me> thusly:
I hope this helps someone else and here is another before/after example
It is a useful correction/addition and I would recommend that you make
a git repository on github with the original version and your patch as >separate commits. Things are *much* easier to find when they are on
github instead of as source archives on various web sites.
My 0.2mg Au
--
In article <118h7q4$3icrv$2@news.xmission.com>, Richard <> wrote:
ECNeilson <eric@neilsonhart.com> spake the secret code >><117cof5$tinj$1@dont-email.me> thusly:
I hope this helps someone else and here is another before/after example
It is a useful correction/addition and I would recommend that you make
a git repository on github with the original version and your patch as >>separate commits. Things are *much* easier to find when they are on
github instead of as source archives on various web sites.
My 0.2mg Au
This is not FIG Forth filosofy. FIG distributed source listings.
The FIG sources are cast in stone, just as well.
You are supposed to adapt the source to your needs.
Trivial modification are not worth a website.
It is a useful correction/addition and I would recommend that you makeI'll do this. I have a couple of Git repos already, so I'll create a
a git repository on github with the original version and your patch as separate commits. Things are *much* easier to find when they are on
github instead of as source archives on various web sites.
It is a useful correction/addition and I would recommend that you make
a git repository on github with the original version and your patch as separate commits. Things are *much* easier to find when they are on
github instead of as source archives on various web sites.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 53:40:40 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,448 |