From: Jakub Narebski <jnareb@gmail.com>
To: Maaartin <grajcar1@seznam.cz>
Cc: git@vger.kernel.org
Subject: Re: OT: This forum
Date: Mon, 11 Oct 2010 17:29:04 -0700 (PDT) [thread overview]
Message-ID: <m3sk0cdzkn.fsf@localhost.localdomain> (raw)
In-Reply-To: <loom.20101012T012512-764@post.gmane.org>
Maaartin <grajcar1@seznam.cz> writes:
> I read this forum using
> http://post.gmane.org/post.php?group=gmane.comp.version-control.git
> and it sort of works. Except that finding own old posting is quite impossible,
> even when I try searching for the subject, and/or author, and/or pieces of text
> in any combination. It finds some posting, but it misses others, whatever I do.
> Except that I don't know how to attach a file. Except that I'd expect to see a
> thread containing a new reply somewhere on the first page instead of on the
> 14th. Except that replies to emails I get (answers to my threads) goes to their
> author instead of to the forum.
>
> Is there a better way for using this forum/mailing list? However, I'd like to
> avoid getting daily dozens of emails.
I personally read git mailing list (and reply) using GMane's NNTP
interface.
You can read postings using any Usenet news reader, for example Gnus
from GNU Emacs / XEmacs, or KNode from Kontact, ory any mail client
supporting Usenet, using news.gmane.org as server, and subscribing to
gmane.comp.version-control.git (it is described on Gmane). Those news
readers usually support threading.
But please remember to reply via email, and rather not cut Cc list.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-10-12 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 23:35 OT: This forum Maaartin
2010-10-12 0:11 ` Chris Packham
2010-10-12 0:29 ` Jakub Narebski [this message]
2010-10-13 14:35 ` Scott R. Godin
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=m3sk0cdzkn.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=grajcar1@seznam.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.