<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ben Finney wrote:
<blockquote cite="mid:87ws1mf3d0.fsf@benfinney.id.au" type="cite">
<pre wrap="">David Stanek <a class="moz-txt-link-rfc2396E" href="mailto:dstanek@dstanek.com"><dstanek@dstanek.com></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">On Thu, Nov 19, 2009 at 4:24 PM, Ross Lawley <a class="moz-txt-link-rfc2396E" href="mailto:ross.lawley@gmail.com"><ross.lawley@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Ned,
Can I have write access to the repo? Username: Rozza.
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">Can't you clone it on bitbucket?
</pre>
</blockquote>
<pre wrap=""><!---->
Someone needs to teach Ned how to collaborate using Mercurial and
Bitbucket, I think.
Cloning Ned's repository and making changes available in one's clone is
the right way to do it (not least because it means one doesn't need
write access to Ned's repository in order to contribute revisions to his
code base), but that will only work if Ned gets some learnin' from
someone.
</pre>
</blockquote>
There are many things I don't know about hg and BB, and I would be glad
to learn. Chiding is all well and good, but teaching is more
effective! Even a pointer to a focused tutorial would be helpful.
Mercurial offers a bewildering array of options for moving code around:
cloning, forking, branching, patch queues, bundles, maybe more.<br>
<br>
I made the repo at holger's request, but nothing has happened there yet.<br>
<br>
--Ned.<br>
<br>
</body>
</html>