public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Stan Shebs <shebs@apple.com>
Cc: xconq <xconq7@sources.redhat.com>, <xconq-hackers@lists.sourceforge.net>
Subject: Re: RH vs SF
Date: Mon, 07 Feb 2005 19:34:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0502071419570.32012-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <4207BA21.10609@apple.com>


Hi Stan,

On Mon, 7 Feb 2005, Stan Shebs wrote:

> So it seems that the sourceforge site is up and running smoothly, no?

For the most part.

> to do with the bits at Red Hat. At the very least, everything there
> should go into a readonly mode, with forwarding to the SF site, so
> as to prevent inadvertant forking.

Sounds reasonable.

> A bigger project would be to copy the old repository and mail
> archives. I can ask RH's "overseers" about how to get the data, dunno
> about splicing CVS history into SF's repository. 

I would recommend a separate 'xconq-old' top-level module. The 
locations (and names) of some files have changed, and it probably 
make any splicing task rather challenging. If I had access to 
the RCS files on SF, I would consider taking up the challenge of 
merging the history directly into the existing 'xconq' module. 
However, I don't, _only the SF admins have that access, AFAIK. If 
you can get the RCS files from RH, we can ask the SF admins to 
pull them into 'xconq-old' or something like that. The SF docs 
advertize that their admins are willing to do such things for a 
project.

Eric

P.S. If you want to be a project admin for Xconq on the SF site, 
let me know the SF username I should add. It's your project, so I 
think you should be an admin....

      reply	other threads:[~2005-02-07 19:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 18:57 Stan Shebs
2005-02-07 19:34 ` Eric McDonald [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=Pine.LNX.4.44.0502071419570.32012-100000@leon.phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --cc=shebs@apple.com \
    --cc=xconq-hackers@lists.sourceforge.net \
    --cc=xconq7@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).