From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: moeller0 <moeller0@gmx.de>, Rich Brown <richb.hanover@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bufferbloat.net - Organizing, curating, and workflow
Date: Sun, 12 Jun 2016 11:27:51 -0700 [thread overview]
Message-ID: <CAA93jw5MC_4iHd1yTFvUm7z+paRgZv-1xnF8is1UDn5ZmpU41g@mail.gmail.com> (raw)
In-Reply-To: <87fusii86q.fsf@toke.dk>
On Sun, Jun 12, 2016 at 11:16 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> moeller0 <moeller0@gmx.de> writes:
>
>> So how do I contribute changes to existing pages? The cake page has
>> some inaccuracies regarding VDSL2 encapsulation that I would like to
>> fix…
>
> Clone the repo at https://github.com/tohojo/bufferbloat-net/, make
> changes to the right markdown file and submit a pull request with the
> change :)
Arguably it will be faster as expertise is gained to allow more (most
or all) of the core authors direct access to the primary github repo,
and autopublication is possible with a post-push hook.
It does help to run hugo locally to preview your fixes as you go along.
One of the big "fixes" inherent in this design is that hugo supports a
"draft" concept, where stuff can be iterated on inside of git by one
or more parties before it makes it to the public web. I have a problem
in that I'm always working on 6 things at once and have had a tendency
to realize "oh, that's a topic that needs more work", and yet never
get around to fleshing out that topic, in part, because I forget it's
essentially a broken link.
I envy those that can sit down on a conventional wiki, start, and two
hours later write "the end" and move on. That process for me takes
days, weeks, (or years!). I really liked adopting the bloggy format
for blog.cerowrt.org, as my natural metíer is the rant. I must have
30+ more articles in draft form in git at the moment, there.
> -Toke
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next prev parent reply other threads:[~2016-06-12 18:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1225.1465559858.3642.bloat@lists.bufferbloat.net>
2016-06-10 15:27 ` [Bloat] bufferbloat.net is sorely missed Rich Brown
2016-06-10 15:47 ` Dave Taht
2016-06-10 16:19 ` Rich Brown
2016-06-10 17:08 ` Kevin Darbyshire-Bryant
2016-06-10 17:13 ` Outback Dingo
2016-06-10 18:05 ` Dave Taht
2016-06-10 18:17 ` Steinar H. Gunderson
2016-06-10 18:18 ` Rich Brown
2016-06-10 18:23 ` Dave Taht
2016-06-11 12:07 ` Toke Høiland-Jørgensen
2016-06-11 17:58 ` Dave Taht
2016-06-11 18:29 ` Toke Høiland-Jørgensen
2016-06-11 18:32 ` Toke Høiland-Jørgensen
2016-06-11 19:09 ` Dave Taht
2016-06-11 19:24 ` [Bloat] bufferbloat.net is sorely missed/Now it's back! Rich Brown
2016-06-11 20:05 ` Toke Høiland-Jørgensen
2016-06-11 21:31 ` Dave Taht
2016-06-12 17:49 ` [Bloat] Bufferbloat.net - Organizing, curating, and workflow Rich Brown
2016-06-12 18:02 ` Toke Høiland-Jørgensen
2016-06-12 18:13 ` moeller0
2016-06-12 18:16 ` Toke Høiland-Jørgensen
2016-06-12 18:24 ` moeller0
2016-06-12 18:25 ` Toke Høiland-Jørgensen
2016-06-12 18:27 ` Dave Taht [this message]
2016-06-12 18:33 ` Toke Høiland-Jørgensen
2016-06-13 13:25 ` Rich Brown
2016-06-13 14:05 ` Toke Høiland-Jørgensen
2016-06-13 15:13 ` [Bloat] Bufferbloat.net & LinkChecker Rich Brown
2016-06-13 19:18 ` Toke Høiland-Jørgensen
2016-06-13 14:58 ` [Bloat] Bufferbloat.net - Organizing, curating, and workflow Dave Taht
2016-06-13 15:15 ` Toke Høiland-Jørgensen
2016-06-13 15:39 ` Dave Taht
2016-06-13 10:33 ` [Bloat] bufferbloat.net is sorely missed/Now it's back! Kevin Darbyshire-Bryant
2016-06-13 11:10 ` Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5MC_4iHd1yTFvUm7z+paRgZv-1xnF8is1UDn5ZmpU41g@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=richb.hanover@gmail.com \
--cc=toke@toke.dk \
/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