Presenting a clean history: how to synchronize two repositories.

[Harvey Chapman]

On May 13, 2014, at 4:14 PM, Michael McNeil Forbes <michael.forbes at gmail.com> wrote:

> On May 13, 2014, at 12:43 PM, Harvey Chapman <hchapman-hg at 3gfp.com> wrote:
>> On May 13, 2014, at 3:10 PM, Michael McNeil Forbes <michael.forbes at gmail.com> wrote:
>>> 
>> The method I had thought to use involved maintaining a separate, “abridged” branch in your dev repo for public exposure. You can use the fold command to collapse lots of little checkins into milestones or features. To accept patches or move things back and forth, you can graft or transplant changesets. Then, you only publish the abridged branch.
> 
> How would one publish only the abridged branch?  If it derives from the dev repo, won't it by necessity required the entire dev repo since the changeset hashes are based on the entire history?
> 
> Unless you mean use convert as I suggested, in which case I am then looking for some people with experience doing this so I understand the potential pitfalls, and how to implement the grafting/etc. across the two repos.

The branches are basically unrelated in terms of the DAG so pushing just the abridged branch doesn’t require the dev branch to be pushed. It’s like your convert solution I think, but probably easier to manage.

Harvey