Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Gnus repositories - corruption of gnus-uu.el and gnus-xmas.el fixed
Date: Sat, 15 Aug 2009 10:25:37 +0200	[thread overview]
Message-ID: <87fxbtfpq6.fsf@randomsample.de> (raw)
In-Reply-To: <87hbw9a4kt.fsf_-_@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sat, 15 Aug 2009 10:01:22 +0200")

Reiner Steib <reinersteib+gmane@imap.cc> writes:
> Andreas and David also have set up git trees of the Gnus repository.
> (I don't know if they are intended for public use, so I don't post the
> URLs.)

Well, I merely didn't advertise it because I'm not sure if it's stable
enough, and it's not an "official" repo in any way. That being said,
people may of course clone from it:

(git|http) ://randomsample.de/gnus.git

CVS commits get synced automatically, usually within the hour.

-David



  reply	other threads:[~2009-08-15  8:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13 11:57 git/hg Gnus repository David Engster
2008-12-13 15:10 ` Reiner Steib
2008-12-13 15:35   ` David Engster
2009-08-15  8:01     ` Gnus repositories - corruption of gnus-uu.el and gnus-xmas.el fixed (was: git/hg Gnus repository) Reiner Steib
2009-08-15  8:25       ` David Engster [this message]
2009-08-29 10:10       ` Gnus repositories - corruption of gnus-uu.el and gnus-xmas.el fixed Adam Sjøgren
2008-12-14 16:53 ` git/hg Gnus repository Kalle Olavi Niemitalo
2008-12-14 22:10   ` David Engster
2008-12-15 22:30     ` David Engster
2009-02-14 21:44       ` Eric Schulte
2009-02-15 16:18         ` David Engster
2009-02-15 18:09           ` Eric Schulte
2009-06-30  8:13           ` Andreas Seltenreich
2009-06-30  8:28             ` David Engster
2009-07-05 22:40               ` Miles Bader
2009-07-06  9:46                 ` David Engster
2009-07-08 18:58                   ` 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=87fxbtfpq6.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --cc=ding@gnus.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).