public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: jemarch@gnu.org (Jose E. Marchesi)
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	 cgen@sourceware.org,  nickc@redhat.com
Subject: Re: Converting CGEN from CVS to git
Date: Mon, 22 Apr 2019 09:43:00 -0000	[thread overview]
Message-ID: <87y342bclx.fsf@gnu.org> (raw)
In-Reply-To: <20190421213226.GC2737@embecosm.com> (Andrew Burgess's message of	"Sun, 21 Apr 2019 22:32:26 +0100")

    
    
      - Maybe someone can confirm that they can checkout the new
        repository, and even better test it.  Instructions for how I've
        been testing this against binutils-gdb are below.  Then,

Works for me.
I tried with both the in-tree and out-of-tree approaches.
    
      - If this is possible it would be great to make the old CVS
        read-only so nobody accidentally commits anything there.  I don't
        have permissions to do anything like this, finally
    
      - Update the web pages to point at the new git repository.  I have a
        patch for this below, and I _might_ even be able to commit it.  I
        wont know until I try I guess.

+1

      reply	other threads:[~2019-04-22  9:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 19:50 Andrew Burgess
2019-02-02  9:35 ` Jose E. Marchesi
2019-02-03 16:30 ` Frank Ch. Eigler
2019-02-04  8:25   ` Jose E. Marchesi
2019-02-04 13:51     ` Frank Ch. Eigler
2019-02-04 16:33   ` Andrew Burgess
2019-03-03 22:38     ` Frank Ch. Eigler
2019-03-06 13:28       ` Andrew Burgess
2019-03-27 14:32         ` Andrew Burgess
2019-03-27 20:09           ` Frank Ch. Eigler
2019-04-21 16:23             ` Andrew Burgess
2019-04-21 16:42               ` Frank Ch. Eigler
2019-04-21 19:39                 ` Andrew Burgess
2019-04-21 21:32             ` Andrew Burgess
2019-04-22  9:43               ` Jose E. Marchesi [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=87y342bclx.fsf@gnu.org \
    --to=jemarch@gnu.org \
    --cc=andrew.burgess@embecosm.com \
    --cc=cgen@sourceware.org \
    --cc=fche@redhat.com \
    --cc=nickc@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).