Import patches for the specified revision

[Martin Geisler]

Kevin Bullock <kbullock+mercurial at ringworld.org> writes:

> On 15 Dec 2011, at 8:27 PM, nemo wrote:
>
>> I'm developing a website on which users can browser their hg repos and
>> edit source codes on line, just like what github can do.
>> 
>> In case multi users edit the same file at the same time, I must keep my
>> hand off the working copy. So I need the --bypass option.
>
> Stop right there. I'm pretty sure what GitHub does when you click the
> 'edit' button is to _first_ create a fork (or more accurately, adds a
> job to their queue to create a fork in the background), and then pops
> open an editor. So your changes go in a separate working copy on the
> server. This neatly avoids the whole problem you're seeking a solution
> to.

I know nothing about how GitHub is implemented, but I would not expect
them to have working copies lying around. It's unnecessary and slow when
the working copy is huge. It's much faster to do a commit directly at
the right spot in the changeset graph. This can be done with a small
Mercurial extension and I guess Git will let you do that as well.

However, if writing such an extension is difficult, then doing as you
say will be an easy work-around.

-- 
Martin Geisler

Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial/attachments/20111216/3620a903/attachment.pgp>