unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: How to search on emacs-devel?
Date: Wed, 09 Mar 2022 14:01:32 -0800	[thread overview]
Message-ID: <87k0d2lr9f.fsf@ericabrahamsen.net> (raw)
In-Reply-To: jwvsfrqiz6s.fsf-monnier+emacs@gnu.org

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> - A bidirectional IMAP <-> Git gateway.
>> But this bit would live on a server someplace, not locally?
>
> Right.
>
>>> - an nngit backend (not just read-only).
>> And this bit would I guess need to be a wrapper around a different nn*
>> backend, since git would only be the transport, the messages themselves
>> might be stored as mbox or maildir or something.
>
> I think it'd need its own file layout because we'd want to make sure
> Git's conflict resolution does "the right thing".
>
>> This would also compete for the "nngit" name with the
>> non-existent-yet-historically-inevitable backend that presents
>> a news-like interface to the branches and commits in a git repository.
>
> Yes, it shouldn't be called "nngit".  Instead the file-layout system
> would have its own name, like `MailGit`, `Gail`, `GitBox`, or whoknowswhat.

Gotcha. I was thinking this would be a git interface to whatever mail
store happened to be out there in the wild, but you're describing
something where it's the IMAP server that interfaces with "the wild",
and git is just the internal store? I guess I don't see a major
advantage to just using IMAP directly...




  reply	other threads:[~2022-03-09 22:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 18:51 How to search on emacs-devel? Eric Abrahamsen
2022-03-09 18:59 ` Eric Abrahamsen
2022-03-09 19:24   ` Stefan Monnier
2022-03-09 19:49     ` Eric Abrahamsen
2022-03-09 21:46       ` Stefan Monnier
2022-03-09 22:01         ` Eric Abrahamsen [this message]
2022-03-09 22:12           ` Stefan Monnier
2022-03-09 22:23             ` Eric Abrahamsen
2022-03-10  5:49   ` Kyle Meyer
2022-03-10  6:51     ` Eli Zaretskii
2022-03-10 17:43       ` Eric Abrahamsen
2022-03-10 17:56         ` Eli Zaretskii
2022-03-10 18:12           ` Eric Abrahamsen
2022-03-10 17:54     ` Eric Abrahamsen
  -- strict thread matches above, loose matches on Subject: below --
2022-03-08 15:09 dalanicolai
2022-03-08 15:17 ` dalanicolai
2022-03-08 15:57   ` andrés ramírez
2022-03-08 16:06     ` dalanicolai
2022-03-08 17:49 ` Philip Kaludercic
2022-03-08 18:13   ` Eric Abrahamsen
2022-03-09 13:34     ` Robert Pluim
2022-03-09 15:44       ` Eric Abrahamsen
2022-03-09 17:36       ` Stefan Monnier
2022-03-09 17:43         ` Andreas Schwab
2022-03-10 15:50       ` Felix Dietrich
2022-03-10 16:46         ` Felix Dietrich
2022-03-09 11:41   ` dalanicolai

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k0d2lr9f.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).