[PATCH] Added ability to clone from a local repository to a (new) remote one

[Sean Meiners]

On Tuesday 20 June 2006 12:08, Eric Hopper wrote:
> On Tue, Jun 20, 2006 at 11:13:35AM -0700, Sean Meiners wrote:
> > Maybe what we really need is a separate command, but for our use case
> > this is necessary. We have a large tool chain built around centralized
> > revision control (we currently use TLA). A normal workflow for a
> > developer is: 1) create new source tree (tla init-tree / hg init)
> > 2) add files (tla add-id / hg add)
> > 3) check it into the source control file server (tla import / hg ?)
> > 4) tell one of our build machines to pull the source from the central
> > server and build it.
>
> This is an interesting use case, and I've often wished for a way to
> easily manipulate the paths without having to edit .hg/hgrc.
>
> Here's my idea:
>
> hg paths --add default-push remote-repo
> hg paths --remove path-to-remove
>
> This would make editing paths trivial.  Making a specialized command set
> for setting up hgrc seems a little silly.  But this particular use-case
> is one I encounter frequently, and this particular instance would be
> very helpful.
>
> It's not quite as automatic as push to remote setting default-push
> automatically.  But that's a default behavior I think is of dubious
> general usefulness.

That's why I decided to make the feature 'opt-in' in the most recent version 
of the patch. This way it's as simple as adding '-u' to the command line for 
those who want it and those who don't don't have to do anything at all.

>
> Have fun (if at all possible),

-- 
Sean Meiners
sean.meiners at linspireinc.com


Perl - $Just @when->$you ${thought} s/yn/tax/ &couldn\'t %get $worse;