Gnus development mailing list
 help / color / mirror / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: ding@gnus.org
Subject: Re: git/hg Gnus repository
Date: Sun, 15 Feb 2009 10:09:51 -0800	[thread overview]
Message-ID: <87wsbra7ww.fsf@gmail.com> (raw)
In-Reply-To: <87bpt3y8pu.fsf@randomsample.de> (David Engster's message of "Sun, 15 Feb 2009 17:18:37 +0100")

David Engster <deng@randomsample.de> writes:

> "Eric Schulte" <schulte.eric@gmail.com> wrote on top:
>> Now that this has been accomplished, is there any chance of a publicly
>> readable git repo tracking the cvs gnus repo?  Thanks -- Eric
>
> I was only able to import roughly the last year of changes, so my
> private git repo only contains a subset of files. The others are simply
> copied without history.
>
> For having a useful git clone with the full history, one would still
> need a copy of the full CVS repo for a conversion. Using git-cvsimport
> over the net would take ages and hammer the server to no end.
>
> -David

I don't think history is as important as tracking new changes moving
forward.  This isn't anything more than a convenience, but I find it
very nice to be able to use git to, for example, track Emacs
development.

Best -- Eric



  reply	other threads:[~2009-02-15 18:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13 11:57 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       ` Gnus repositories - corruption of gnus-uu.el and gnus-xmas.el fixed David Engster
2009-08-29 10:10       ` 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 [this message]
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=87wsbra7ww.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --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).