[PATCH] Updated patch to add remote destination support with suggestions from

[Bryan O'Sullivan]

On Wed, 2006-06-21 at 16:12 -0700, Sean Meiners wrote:

> My problem is that even though updating the hgrc file seems like a small 
> thing, it would be a huge problem for us.

I think you misunderstand what I'm getting at.  It's trivial to add the
bulk of your functionality, and the hgrc updating bit requires consensus
first.  But there's a little more to it:

Since the two hunks of work are logically distinct (e.g. you can imagine
updating hgrc after a pull, not just after a push), they belong in
separate patches anyway, so people can see "OK, this is the change that
introduces remote clone" and "this other change updates hgrc for me"
when browsing history later.

> I can't figure out how to make patchbomb/mercurial to send just one patch when 
> my local tree (where I've made tag 0.9 the tip) has multiple commits from me. 

It's designed to send one patch per changeset.  I imagine that it could
be extended to send one big patch if that were desired.

> Should I just send a 'hg diff -r .. -r ..' instead?

Yes, at least for now.

	<b

-- 
Bryan O'Sullivan <bos at serpentine.com>