> I had a few bug reports on the kernel that I think
> never got included in the mainline plan9.
> Should I make pull requests?
I think I could create a fork repository for
contributions.
> Is there anyway this github repo could be synchronized with
> the main plan9-labs repo?
I have all the scr
This is great! Thx!
I had a few bug reports on the kernel that I think
never got included in the mainline plan9. Should I make pull requests? Is there
anyway this github repo could be synchronized with the main plan9-labs repo?
On Dec 8, 2014, at 11:52 AM, David du Colombier <0in...@gmail.com>
> You could have used --aggressive garbage collection,
> it reduces the package to exactly 100MB.
Yes. Unfortunately, this is too late for the GitHub
repository now. On the other side, it would be only
10 MB smaller.
--
David du Colombier
David du Colombier <0in...@gmail.com> wrote:
|I've recently converted my archives of /n/sources/plan9
|to Git and uploaded the repository on GitHub.
|
|https://github.com/0intro/plan9
Thank you.
|It contains the entire history of /n/sources/plan9,
|one commit per day, from December 12, 2002
I've recently converted my archives of /n/sources/plan9
to Git and uploaded the repository on GitHub.
https://github.com/0intro/plan9
It contains the entire history of /n/sources/plan9,
one commit per day, from December 12, 2002 to today,
excluding the binaries and empty directories.
I tried to
