From: Marc Joliet <marcec@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Wiki suggestions
Date: Mon, 13 Jul 2015 19:21:54 +0200 [thread overview]
Message-ID: <20150713192154.3465d3ae@thetick> (raw)
In-Reply-To: <20150713163009.GE15535@twin.jikos.cz>
[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]
Am Mon, 13 Jul 2015 18:30:09 +0200
schrieb David Sterba <dsterba@suse.com>:
> On Mon, Jul 13, 2015 at 01:18:27PM +0200, Marc Joliet wrote:
> > Am Mon, 13 Jul 2015 06:56:17 +0000 (UTC)
> > schrieb Duncan <1i5t5.duncan@cox.net>:
> >
> > > Marc Joliet posted on Sun, 12 Jul 2015 14:26:04 +0200 as excerpted:
> > >
> > > > I hope it's not out of place, but I have a few suggestions for the Wiki:
> > >
> > > Just in case it wasn't obvious... The wiki is open to user editing. You
> > > can, if you like, get an account and make the changes yourself. =:^)
> > >
> > > Of course, it's understandable if your reaction to web and wiki
> > > technologies is similar to mine, newsgroups and mailing lists (in my case
> > > via gmane.org's list2news service, so they too are presented as
> > > newsgroups) are your primary domain, and you tend to treat the web as
> > > read-only so rarely reply on a web forum, let alone edit a wiki. I've
> > > never gotten a wiki account here for that reason, either, or I'd have
> > > probably gone ahead and made the suggested changes...
> > >
> > > But with a bit of luck someone with an existing (or even new) account
> > > will be along to make the changes...
> >
> > It's partially a "read-only" habit, but it's also that I'm just not confident
> > in deciding whether those actually *are* good suggestions, or put differently:
> > it's the public face of btrfs, and I don't want to accidentally do something to
> > "ruin" it (to use some hyperbole).
>
> All your suggesstions are good, adding more articles/videos/talks should
> be easy as there's a section for that already. The news section is
> mostly written by me but if you keep your entries consistent with the
> rest then it's ok.
>
> There are a few people who watch over new wiki edits and fix/enhance
> them if needed. You can't do too much damage unless you really want to.
OK, I'll make the changes then (sans kernel log).
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-13 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 12:26 Wiki suggestions Marc Joliet
2015-07-13 6:56 ` Duncan
2015-07-13 11:18 ` Marc Joliet
2015-07-13 16:30 ` David Sterba
2015-07-13 17:21 ` Marc Joliet [this message]
2015-07-13 17:33 ` Marc Joliet
2015-07-14 8:09 ` David Sterba
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=20150713192154.3465d3ae@thetick \
--to=marcec@gmx.de \
--cc=linux-btrfs@vger.kernel.org \
/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