![]() ![]() Now imagine that the unthinkable happens: you have discovered a fatal bug in the project. So we've been happily typing away at our source in the 'risky' branch where our experimental feature lives. When you're done with the feature, you can merge the branches to update the main branch with the changes in the experimental feature branch even if you've made changes to the main branch! It's based on simple principles, but it's almost magical to watch. Mercurial's named branches to the rescue! With a named branch, you can work on the experimental feature and the main branch of the project at the same time and in the same directory. On top of that, you're not going to want to have to keep track of and make the same bug fix to the files again after you launch a new version of the project which incorporates the experimental feature. ![]() The fix is simple, but to do it, you're going to need to make changes to the original versions of the files that existed before you started the new experimental feature. Now assume that someone finds a critical bug in your project. There may even be other developers working on the project at the same time. In the meantime, people are using your project and may find bugs which will need fixing. To make this feature work, you're going to need to make sweeping changes across the project. This feature seems like a good idea, but it's a bit of a gamble and you're going to need to see it in action before you're sure it should become a permanent part of the project. The Basics (Creating and Committing Repositories)įeel free to skip this section if you're already familiar with the basics of TortoiseHg usage.Ĭonsider the following scenario: you're about to embark upon a new experimental feature.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |