But the hex IDs are the only ones that are valid when talking
with another developer, or even when working between repositories on the same
machine, as we see here.
306 | Chapter 10: Large Projects
Of course, the latter has the advantage of preserving files that are not kept under
revision control.
??? Mercurial keeps all of its revision control metadata, including the entire repository,
in a single .hg directory under the project root. You can recursively copy
this .hg directory over the .hg directory of another repository and then perform
an hg update --clean from the target repository to update the working copy
(which may contain extra, non-version-controlled files).
Mercurial also has support for named branches, which are separate branches of development
within one repository. This support has been mature since version 0.9.4.
However, named branches complicate certain aspects of using Mercurial, and they
are a somewhat advanced feature. Named branches are preferable for long-lived
development branches, while branching by cloning is still preferred for feature
branches. Chapter 8 of Distributed Revision Control with Mercurial goes into detail
about branching and merging (http://hgbook.red-bean.com/hgbookch8.html).
Database Migrations
When working with large Rails projects, especially those with multiple developers or
feature branches, an issue that frequently comes up is synchronizing database migrations.
Pages:
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465