From: Ted Zlatanov <tzz@lifelogs.com>
To: info-gnus-english@gnu.org
Subject: Re: Proposal for a crazy new Group type
Date: Mon, 13 Aug 2007 12:14:59 -0500 [thread overview]
Message-ID: <m2ir7js6ek.fsf@lifelogs.com> (raw)
In-Reply-To: <85mywwq58i.fsf@lola.goethe.zz>
On Sun, 12 Aug 2007 14:58:37 +0200 David Kastrup <dak@gnu.org> wrote:
DK> I have been thinking about how Emacs could help with navigating branch
DK> histories of git (a version control system), and the problem is that
DK> one needs to have delayed action and so on if one wants to hope to
DK> keep abreast of large repositories.
...
DK> Anyway: basically all the functionality that is required for a News
DK> source, threading, message ids, header prefetch, article on request:
DK> it is all available.
I think this is an interesting idea, but the ding mailing list would be
a better place to propose it. I personally don't use git, but can see
the use for all kinds of vc backends, so it may be better to make this
generically tied with the Emacs vc code.
Ted
prev parent reply other threads:[~2007-08-13 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 12:58 David Kastrup
2007-08-13 17:14 ` Ted Zlatanov [this message]
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=m2ir7js6ek.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=info-gnus-english@gnu.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;
as well as URLs for NNTP newsgroup(s).