On Thu, Mar 17, 2011 at 3:04 PM, Steve Borho <[email protected]> wrote:
> On Thu, Mar 17, 2011 at 2:41 PM, Joe Schneider <[email protected]> wrote:
>> With the pre-2.0 UI I was able to use the synchronize dialog to pull a
>> targeted changeset or changesets from a remote repository.  This is useful
>> when I want to pull a particular set of changes from a co-worker, but I
>> don't want other private changes in that co-worker's repository.
>>
>> In the 2.0 UI the only way I've found to do this is to first do an
>> "incoming" operation, then before Accepting the changes, right-click the
>> branch or changeset you want to pull and use the Pull to here... option.
>> This is particularly painful if the remote repository has lots/large
>> changesets that I don't care about, because they are pulled in the bundle by
>> the incoming operation and takes a lot of time.  Is there a way to pull a
>> targeted changeset from a remote repository without first running the
>> incoming operation?
>
> No.  You're only other option is to type into the log widget:
>
> hg pull OTHER -r REV

There are two other solutions for this, but they both require workflow changes.

1.  I believe bookmarks are intended to solve this issue.  You
bookmark the head you are interested in, then push/pull it back and
forth.

2. You can make a local clone of your own repository (using hardlinks
so it uses very little space, and do not checkout a working
directory).  You call this clone: buddy-incoming and pull all of your
friend's changesets into it.  Now you can open this up in the
Workbench and selectively push revisions into your repository.

-- 
Steve Borho

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to