Hans sent the following mail to our alias, I'm filing a bug so we can keep record of the request > Hi, > > Could you provide Mats Lidell with access to the XEmacs overlay? He will > be the new xemacs developer, and this way he can be productive right > away. I'm asking this as the old xemacs maintainer, but I've also > checked with ulm on IRC. > > Preferred nick: matsl > > SSH public key: > > ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA04UZuJZWRvAUMfb3plwM+hbDpsmIAvoua+5qGZByNqOaOStE88mDcD7LzAmfR+66s+EXc2GTZtkKh14Efq5ym+W+yHH6e5RXrJwJNm0V+DOyxojuLTo5iAwJwlcVg1FJFmcI6F5XGFDlX/nbSwBra6fP50l1lAttbjDpx0DfXts= matsl@spencer > > > Kind regards, > > Hans
I just noticed that xemacs overlay is still in SVN. Since we are migrating them slowly to git, do I have your permission to migrate the overlay first? (if so, I'll file a separate bug for that)
(In reply to comment #1) > I just noticed that xemacs overlay is still in SVN. Since we are migrating > them slowly to git, do I have your permission to migrate the overlay first? > (if so, I'll file a separate bug for that) I think migration was discussed earlier and the emacs guys want to stick with SVN...
(In reply to comment #2) > I think migration was discussed earlier and the emacs guys want to stick > with SVN... Infra wants to stick to one SCM and thus we started migrating every SVN repo to Git. Even if you want to stick with SVN it is fine now, but it has to be migrated one day, apologies if you don't like that decision. Anyway, our SVN setup works with htpasswd hashes instead of SSH keys, thus I need such a hash to create the account, so please send it by mail to me only for security reasons.
Adding ulm since I think he told me that we should stick with SVN.
(In reply to comment #1) > I just noticed that xemacs overlay is still in SVN. Since we are migrating > them slowly to git, do I have your permission to migrate the overlay first? > (if so, I'll file a separate bug for that) No need for that, there's bug 418443 already which can be reopened. Including a first set of rules for svn2git. (In reply to comment #4) > Adding ulm since I think he told me that we should stick with SVN. I'd rather do the migration now than later. However, fauli has raised objections against it. Adding emacs team to CC.
(In reply to comment #5) > However, fauli has raised objections against it. Hm, not sure if this is a precise account of it. In fact he only said that he sees no need for a move. Fauli, can you please comment?
No reply, so I think we should proceed. I've reopened bug 418443.
Today I check my Gentoo mail and I think I can give my ok to go on.
What is the status here? Has access been granted?
(In reply to comment #9) > What is the status here? Has access been granted? Yes. If I remember correctly I did an initial test that I could pull from the repo. I have however after that not touched it. So no push yet. I have been focusing on getting the review sessions ready.
seems fixed, reopen please if there is any issue
(In reply to comment #11) > seems fixed, reopen please if there is any issue After I have updated my local branch successfully using "repoman commit" I try to push and get the following error message: fatal: remote error: access denied or repository not exported: /proj/emacs.git Could there be some permission issue or am I doing something wrong?
(In reply to comment #12) > [..] I try to push and get the following error message: > > fatal: remote error: access denied or repository not exported: > /proj/emacs.git I have just added your pubkey from LDAP to gitolite and granted write permissions to proj/emacs to you. Please try again.
(In reply to comment #13) > (In reply to comment #12) > > [..] I try to push and get the following error message: > > > > fatal: remote error: access denied or repository not exported: > > /proj/emacs.git > > I have just added your pubkey from LDAP to gitolite and granted write > permissions to proj/emacs to you. Please try again. Thanks. After that and fixing some errors on my side I could finally push.
