Hi Stuart and Lex,
The fast-export script that Lex mentioned works quite well. I used it to
create a (temporary) mirror of the Mercurial repo on GitHub:
https://github.com/michel-kraemer/asciidoc
I was able to preserve the complete history and all tags!
From there it should be pretty easy to move to the asciidoc
organization once the permissions have been granted.
Please let me know if I can do anything else.
Cheers,
Michel
Am 29.11.2013 03:25, schrieb Stuart Rackham:
On Fri, Nov 29, 2013 at 1:52 PM, Lex Trotman <[email protected]
<mailto:[email protected]>> wrote:
On 29 November 2013 08:53, Stuart Rackham <[email protected]
<mailto:[email protected]>> wrote:
Hi Lex
That would be great if you could take this on -- your
encyclopedic knowledge of AsciiDoc and your having answered more
questions
on this list than anyone makes you really well qualified for this
task.
The first job would be to copy the current Google Code Hg repo
to a new canonical repo on Github at
https://github.com/asciidoc/asciidoc.
It doesn't exist at the moment: as per Dan's email at the
start of the thread, currently only Dan, myself and Charbel
Bitar are
members of the Github asciidoc organization
(https://github.com/asciidoc).
@Dan: How do we go about adding Lex to the team? What is ownership /
membership protocol for https://github.com/asciidoc?
This can go ahead if there is no dissension on using the existing
https://github.com/asciidoc organization (there's no
intrinsic reason for using the github.com/asciidoc
<http://github.com/asciidoc> organization on Github,
but it has the name and it already exists).
The advantage of organisations to a mature project like Asciidoc is
that it allows forward looking branches to be in separate
repositories, so they are less likely to impact the stable branch,
but they are still connected to the overall organisation.
So for example if an effort to port Asciidoc to Python3 was started
it could be in a separate repository and there is less risk of
Python3 only code leaking into the Python2 version.
Its a sensitive point just now because three other projects I
monitor have recently had accidental pushes of large clumps of
changes to the wrong branch, and its a bugger to clean up if it
isn't noticed immediately and other people have pulled those changes.
That's a good point, repos with multiple long-living branches have
always made me uncomfortable.
Cheers
Lex
Cheers, Stuart
[...]
--
You received this message because you are subscribed to the Google
Groups "asciidoc" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:asciidoc%[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/groups/opt_out.
--
Stuart Rackham
methods: Recruitment Systems
EMail: [email protected] <mailto:[email protected]>
Phone: +64(9)415 6259
Mobile: +64(21)115 7168
--
You received this message because you are subscribed to the Google
Groups "asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/groups/opt_out.
