App-DocKnot
view release on metacpan or search on metacpan
https://www.eyrie.org/~eagle/software/docknot/
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/docknot/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
DocKnot is maintained using Git. You can access the current source on
GitHub at:
https://github.com/rra/docknot
value.
## Support
The [DocKnot web page](https://www.eyrie.org/~eagle/software/docknot/)
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the [issue tracker on
GitHub](https://github.com/rra/docknot/issues). Please be aware that I
tend to be extremely busy and work projects often take priority. I'll
save your report and get to it as soon as I can, but it may take me a
couple of months.
## Source Repository
DocKnot is maintained using Git. You can access the current source on
[GitHub](https://github.com/rra/docknot) or by cloning the repository at:
https://git.eyrie.org/git/web/docknot.git
share/templates/readme-md.tmpl view on Meta::CPAN
mailing list. To subscribe or see the list archives, go to the
[[% support.listname %] list information page]([% support.listurl %]).
[% END %][% IF support.extra %]
[% support.extra %]
[% END %]
[% IF support.github %]
For bug tracking, use the [issue tracker on
GitHub](https://github.com/[% support.github %]/issues).[% ELSE %]
I welcome bug reports and patches for this package at
[% support.email %].[% END %] Please be aware that I tend to be extremely
busy and work projects often take priority. I'll save your report and get
to it as soon as I can, but it may take me a couple of months.[% END %]
## Source Repository
[% name %] [% IF unmaintained %]was[% ELSE %]is[% END %] maintained using
[% vcs.type %]. You can access the current source [% IF vcs.github %]on
[GitHub](https://github.com/[% vcs.github %]) or [% END %]by cloning the
repository at:
[% vcs.url %]
share/templates/readme.tmpl view on Meta::CPAN
[% END %]
[% IF support.github %]
For bug tracking, use the issue tracker on GitHub:
https://github.com/[% support.github %]/issues
[% ELSE %]
I welcome bug reports and patches for this package at
[% support.email %].[% END %] Please be aware that I tend to be
extremely busy and work projects often take priority. I'll save your
report and get to it as soon as I can, but it may take me a couple of
months.[% END %]
SOURCE REPOSITORY
[% name %] [% IF unmaintained %]was[% ELSE %]is[% END %] maintained using [% vcs.type %]. You can access the current source [% IF vcs.github %]on GitHub at:
https://github.com/[% vcs.github %]
or [% END %]by cloning the repository at:
t/data/generate/ansicolor/output/readme view on Meta::CPAN
https://www.eyrie.org/~eagle/software/ansicolor/
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/ansicolor/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
Term::ANSIColor is maintained using Git. You can access the current
source on GitHub at:
https://github.com/rra/ansicolor
t/data/generate/ansicolor/output/readme-md view on Meta::CPAN
## Support
The [Term::ANSIColor web
page](https://www.eyrie.org/~eagle/software/ansicolor/) will always have
the current version of this package, the current documentation, and
pointers to any additional resources.
For bug tracking, use the [issue tracker on
GitHub](https://github.com/rra/ansicolor/issues). Please be aware that I
tend to be extremely busy and work projects often take priority. I'll
save your report and get to it as soon as I can, but it may take me a
couple of months.
## Source Repository
Term::ANSIColor is maintained using Git. You can access the current
source on [GitHub](https://github.com/rra/ansicolor) or by cloning the
repository at:
https://git.eyrie.org/git/perl/ansicolor.git
t/data/generate/c-tap-harness/output/readme view on Meta::CPAN
https://www.eyrie.org/~eagle/software/c-tap-harness/
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/c-tap-harness/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
C TAP Harness is maintained using Git. You can access the current
source on GitHub at:
https://github.com/rra/c-tap-harness
t/data/generate/c-tap-harness/output/readme-md view on Meta::CPAN
## Support
The [C TAP Harness web
page](https://www.eyrie.org/~eagle/software/c-tap-harness/) will always
have the current version of this package, the current documentation, and
pointers to any additional resources.
For bug tracking, use the [issue tracker on
GitHub](https://github.com/rra/c-tap-harness/issues). Please be aware
that I tend to be extremely busy and work projects often take priority.
I'll save your report and get to it as soon as I can, but it may take me a
couple of months.
## Source Repository
C TAP Harness is maintained using Git. You can access the current source
on [GitHub](https://github.com/rra/c-tap-harness) or by cloning the
repository at:
https://git.eyrie.org/git/devel/c-tap-harness.git
t/data/generate/control-archive/output/readme view on Meta::CPAN
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
Configuration updates should be sent to usenet-config@isc.org.
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/control-archive/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
control-archive is maintained using Git. You can access the current
source on GitHub at:
https://github.com/rra/control-archive
t/data/generate/control-archive/output/readme-md view on Meta::CPAN
The [control-archive web
page](https://www.eyrie.org/~eagle/software/control-archive/) will always
have the current version of this package, the current documentation, and
pointers to any additional resources.
Configuration updates should be sent to usenet-config@isc.org.
For bug tracking, use the [issue tracker on
GitHub](https://github.com/rra/control-archive/issues). Please be aware
that I tend to be extremely busy and work projects often take priority.
I'll save your report and get to it as soon as I can, but it may take me a
couple of months.
## Source Repository
control-archive is maintained using Git. You can access the current
source on [GitHub](https://github.com/rra/control-archive) or by cloning
the repository at:
https://git.eyrie.org/git/usenet/control-archive.git
t/data/generate/pam-krb5/output/readme view on Meta::CPAN
https://www.eyrie.org/~eagle/software/pam-krb5/
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/pam-krb5/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
pam-krb5 is maintained using Git. You can access the current source on
GitHub at:
https://github.com/rra/pam-krb5
t/data/generate/pam-krb5/output/readme-md view on Meta::CPAN
Thanks to Sam Hartman for the FAST support implementation.
## Support
The [pam-krb5 web page](https://www.eyrie.org/~eagle/software/pam-krb5/)
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the [issue tracker on
GitHub](https://github.com/rra/pam-krb5/issues). Please be aware that I
tend to be extremely busy and work projects often take priority. I'll
save your report and get to it as soon as I can, but it may take me a
couple of months.
## Source Repository
pam-krb5 is maintained using Git. You can access the current source on
[GitHub](https://github.com/rra/pam-krb5) or by cloning the repository at:
https://git.eyrie.org/git/kerberos/pam-krb5.git
t/data/generate/pgp-sign/output/readme view on Meta::CPAN
https://www.eyrie.org/~eagle/software/pgp-sign/
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/pgp-sign/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
PGP::Sign is maintained using Git. You can access the current source on
GitHub at:
https://github.com/rra/pgp-sign
t/data/generate/pgp-sign/output/readme-md view on Meta::CPAN
value.
## Support
The [PGP::Sign web page](https://www.eyrie.org/~eagle/software/pgp-sign/)
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the [issue tracker on
GitHub](https://github.com/rra/pgp-sign/issues). Please be aware that I
tend to be extremely busy and work projects often take priority. I'll
save your report and get to it as soon as I can, but it may take me a
couple of months.
## Source Repository
PGP::Sign is maintained using Git. You can access the current source on
[GitHub](https://github.com/rra/pgp-sign) or by cloning the repository at:
https://git.eyrie.org/git/perl/pgp-sign.git
t/data/generate/pod-thread/output/readme view on Meta::CPAN
https://www.eyrie.org/~eagle/software/pod-thread/
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/pod-thread/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
Pod::Thread is maintained using Git. You can access the current source
on GitHub at:
https://github.com/rra/pod-thread
t/data/generate/pod-thread/output/readme-md view on Meta::CPAN
## Support
The [Pod::Thread web
page](https://www.eyrie.org/~eagle/software/pod-thread/) will always have
the current version of this package, the current documentation, and
pointers to any additional resources.
For bug tracking, use the [issue tracker on
GitHub](https://github.com/rra/pod-thread/issues). Please be aware that I
tend to be extremely busy and work projects often take priority. I'll
save your report and get to it as soon as I can, but it may take me a
couple of months.
## Source Repository
Pod::Thread is maintained using Git. You can access the current source on
[GitHub](https://github.com/rra/pod-thread) or by cloning the repository
at:
https://git.eyrie.org/web/pod-thread.git
t/data/generate/remctl/output/readme view on Meta::CPAN
https://www.eyrie.org/~eagle/software/remctl/
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/remctl/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
remctl is maintained using Git. You can access the current source on
GitHub at:
https://github.com/rra/remctl
t/data/generate/remctl/output/readme-md view on Meta::CPAN
interface as the UNIX libremctl library.
## Support
The [remctl web page](https://www.eyrie.org/~eagle/software/remctl/) will
always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the [issue tracker on
GitHub](https://github.com/rra/remctl/issues). Please be aware that I
tend to be extremely busy and work projects often take priority. I'll
save your report and get to it as soon as I can, but it may take me a
couple of months.
## Source Repository
remctl is maintained using Git. You can access the current source on
[GitHub](https://github.com/rra/remctl) or by cloning the repository at:
https://git.eyrie.org/git/kerberos/remctl.git
t/data/generate/rra-c-util/output/readme view on Meta::CPAN
https://www.eyrie.org/~eagle/software/rra-c-util/
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/rra-c-util/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
rra-c-util is maintained using Git. You can access the current source
on GitHub at:
https://github.com/rra/rra-c-util
t/data/generate/rra-c-util/output/readme-md view on Meta::CPAN
## Support
The [rra-c-util web
page](https://www.eyrie.org/~eagle/software/rra-c-util/) will always have
the current version of this package, the current documentation, and
pointers to any additional resources.
For bug tracking, use the [issue tracker on
GitHub](https://github.com/rra/rra-c-util/issues). Please be aware that I
tend to be extremely busy and work projects often take priority. I'll
save your report and get to it as soon as I can, but it may take me a
couple of months.
## Source Repository
rra-c-util is maintained using Git. You can access the current source on
[GitHub](https://github.com/rra/rra-c-util) or by cloning the repository
at:
https://git.eyrie.org/git/devel/rra-c-util.git
t/data/generate/wallet/output/readme view on Meta::CPAN
New wallet releases are announced on the kerberos mailing list. To
subscribe or see the list archives, go to:
https://mailman.mit.edu/mailman/listinfo/kerberos
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/wallet/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
wallet is maintained using Git. You can access the current source on
GitHub at:
https://github.com/rra/wallet
t/data/generate/wallet/output/readme-md view on Meta::CPAN
The [wallet web page](https://www.eyrie.org/~eagle/software/wallet/) will
always have the current version of this package, the current
documentation, and pointers to any additional resources.
New wallet releases are announced on the kerberos mailing list. To
subscribe or see the list archives, go to the [kerberos list information
page](https://mailman.mit.edu/mailman/listinfo/kerberos).
For bug tracking, use the [issue tracker on
GitHub](https://github.com/rra/wallet/issues). Please be aware that I
tend to be extremely busy and work projects often take priority. I'll
save your report and get to it as soon as I can, but it may take me a
couple of months.
## Source Repository
wallet is maintained using Git. You can access the current source on
[GitHub](https://github.com/rra/wallet) or by cloning the repository at:
https://git.eyrie.org/git/kerberos/wallet.git
t/data/spin/output/software/docknot/readme.html view on Meta::CPAN
documentation, and pointers to any additional resources.
</p>
<p>
For bug tracking, use the issue tracker on GitHub:
</p>
<pre> https://github.com/rra/docknot/issues</pre>
<p>
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
</p>
<h2>SOURCE REPOSITORY</h2>
<p>
DocKnot is maintained using Git. You can access the current source on
GitHub at:
</p>
t/data/spin/text/input/docknot view on Meta::CPAN
https://www.eyrie.org/~eagle/software/docknot/
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/docknot/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
DocKnot is maintained using Git. You can access the current source on
GitHub at:
https://github.com/rra/docknot
( run in 0.526 second using v1.01-cache-2.11-cpan-87723dcf8b7 )