Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: info-gnus-english@gnu.org
Subject: Proposal for a crazy new Group type
Date: Sun, 12 Aug 2007 14:58:37 +0200	[thread overview]
Message-ID: <85mywwq58i.fsf@lola.goethe.zz> (raw)


Hi,

I have been thinking about how Emacs could help with navigating branch
histories of git (a version control system), and the problem is that
one needs to have delayed action and so on if one wants to hope to
keep abreast of large repositories.

Enter Gnus.

git assigns a unique SHA1 hash to every commit (-> article Id).  Every
commit can have one or more (in the case of a merge) parents (->
References).  Commits can be formatted as mail messages with
"git-format-patch", including inline or external text/x-patch parts
and subject, sender and so on.  One does not actually need to call
git-format-patch to guess the subject line, however: that's the
one-line log info, so it is easy to generate a chronological list of
headers without actually looking into the patches.

If one wants to submit patches, one can easily respool them to an imap
send folder or the draft folder.  It might even make sense to respool
a patch series to a group corresponding to a different branch, but at
the moment having read-only access to a git repository as an ephemeral
group (and probably as a whole, not limited to a branch) providing a
view into the patches would be great.

Anyway: basically all the functionality that is required for a News
source, threading, message ids, header prefetch, article on request:
it is all available.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

             reply	other threads:[~2007-08-12 12:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-12 12:58 David Kastrup [this message]
2007-08-13 17:14 ` Ted Zlatanov

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=85mywwq58i.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --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).