public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Matthieu Vachon <matthieu.o.vachon@gmail.com>
To: "kawa@sourceware.org" <kawa@sourceware.org>
Subject: Re: Fwd: Switching from Subversion to Git
Date: Wed, 26 Aug 2015 14:35:00 -0000	[thread overview]
Message-ID: <CAOTvmo=TXBAmcU4XtD1yz1U7mQ7sUO0qgXSu-18RMyyjRYQ+Rg@mail.gmail.com> (raw)
In-Reply-To: <55DB69D8.2080508@bothner.com>

Note: Re-posting on mailing-list with plain text, sorry.

Hi Per,

Sure I still volunteer to make it happen. As said earlier, I already
performed SVN conversion to git and it's hosted at
https://github.com/maoueh/kawa-fork. Could you take a look and ensure
that is correct with you. It would then be a simple matter of pushing
the SVN mirror to the new Savannah git repository.

It is not fully up-to-date as I had problem syncing with SVN. It
stopped with some weird errors on revision 8527. So, current `master`
branch (equivalent to `trunk`) is at revision 8526. Will try to debug
syncing problem when I find more time.

Is a manual SVN mirror enough or are you aiming more to an fully
automatic mirror? Do you want a bi-directional mirror (git push syncs
to SVN and SVN commit pushes to git) or a one way would be ok (SVN to
git only)?

Regards,
Matt

On Mon, Aug 24, 2015 at 3:01 PM Per Bothner <per@bothner.com> wrote:
>
> [Going back to a discussion from October 2014.]
>
> While I'm reasonably content with Subversion, two things have happened to
> increase my readiness for a switch to Git:
>
> (1) I created a new project on GitHub, so I've been using git more:
>
> https://github.com/PerBothner/DomTerm
>
> (2) More high-profile GNU projects have or will soon switch to Git:
> emacs, gcc, gdb
>
> Emacs specifically is hosted on Savannah:
> http://git.savannah.gnu.org/cgit/emacs.git
>
> If we still have a volunteer to set up a git repository on Savannah
> for Kawa, that would be welcome.  I'm hoping it should be possible to
> initially set it up a git mirror, and then after testing switching it
> over to be the master.  (That seems to be the plan for gcc - to switch
> over an existing repository.)
> --
>         --Per Bothner
> per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2015-08-26 14:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28 20:15 Duncan Mak
2014-08-28 20:30 ` Per Bothner
2014-08-28 20:50   ` Duncan Mak
2014-08-28 20:52     ` mikel evins
2014-09-05 16:58       ` Matthieu Vachon
2014-09-22 21:15         ` Per Bothner
2014-09-24  2:28           ` Matthieu Vachon
2014-09-24  5:40             ` David Pirotte
2014-09-24  5:56               ` mikel evins
2014-09-24 12:16               ` Matthieu Vachon
2014-09-25 18:44                 ` Per Bothner
2014-09-26  6:43                   ` Helmut Eller
2014-10-04  6:04                     ` Fwd: " Matthieu Vachon
2014-10-04  7:02                       ` Per Bothner
2015-08-24 19:01                         ` Per Bothner
2015-08-26 14:35                           ` Matthieu Vachon [this message]
2015-08-27  2:50                             ` Per Bothner
2015-09-15 16:54                               ` Matthieu Vachon
2015-09-15 16:55                                 ` Matthieu Vachon
2014-08-28 20:51   ` mikel evins

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='CAOTvmo=TXBAmcU4XtD1yz1U7mQ7sUO0qgXSu-18RMyyjRYQ+Rg@mail.gmail.com' \
    --to=matthieu.o.vachon@gmail.com \
    --cc=kawa@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).