public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: Sourceware overseers <overseers@sourceware.org>
Cc: dberlin@dberlin.org
Subject: Mercurial users
Date: Wed, 22 Dec 2010 06:46:00 -0000	[thread overview]
Message-ID: <4D115508.9000006@jifvik.org> (raw)

Hi fellow overseers,

The eCos project is switching from CVS to mercurial. One of the things
that was discussed and promised when doing so is that we should be able to
use hg-git to provide a git view into the mercurial master.

Sourceware's current mercurial is a rather elderly 1.2.1, from rpmforge.
That is still the latest version available for RHEL 4 from rpmforge.
However to put it in perspective, the current mercurial is 1.7.2.  hg-git
isn't installed, and they recommend at least hg 1.3 in any case.

So I would like to upgrade sourceware's mercurial, either directly from
upstream sources, or from a rebuild of a more recent source RPM. I would
like to understand who already uses mercurial and how they use it, so I
can tell how they may be affected, warn them when I'm upgrading, and
obviously avoid any breakage should I do so.

I know that Daniel Berlin set up an hg readonly mirror of GCC. I assume
that being very temporarily offline would not be a problem. I am most
interested in projects where mercurial may be being used for write access.

Daniel, if you did anything non-standard I'd need to be aware of, please
let me know.

So please get in touch if you manage (or know of) a project using
mercurial. If no-one replies, I'll assume there are no other users :-).

Jifl

             reply	other threads:[~2010-12-22  1:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22  6:46 Jonathan Larmour [this message]
2010-12-27  7:45 ` Daniel Berlin

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=4D115508.9000006@jifvik.org \
    --to=jifl@jifvik.org \
    --cc=dberlin@dberlin.org \
    --cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).