![]() It's more likely that you'll notice immediately, because Worry, we'll return to this horror scenario later). “ 0.9” tree, confusing your entire team (but don't Insufficient attention, and push those changes into the shared Messy if you had a local “ 0.9” repository, andĪccidentally pulled changes from the shared “ 1.0” Given this, you can imagine that the consequences could be ![]() Your project's “ 0.9” release, and another,Ĭontaining different changes, for the “ 1.0” Your development team might have one shared repository for It's common practice with Mercurial to maintain separateĭevelopment branches of a project in different repositories. $ hg add b $ hg commit -m 'Add file b, this time for real' It was prior to the commit the changeset has been completelyĬommit. Repository's history, and the working directory once againĬommit and rollback have left the working directory exactly as Notice that the changeset is no longer present in the I use the hg rollback command, and Mercurial However, luck is with me-I've caught my errorīefore I pushed the changeset. Repository that I shared with a colleague, the chances are ![]() The commit captured the changes to the file Status after the commit immediately confirms the Here's a mistake that I often find myself making:Ĭommitting a change in which I've created a new file, but (See the section called “Rolling back is useless once you've pushed”įor an important caveat about the use of this command.) Repository, Mercurial remembers what you did. You commit a changeset or pull changes from another Mentioned that Mercurial treats each modification of a In the section called “Safe operation”, I Of problems, and to handle them appropriately. Highly capable features that will help you to isolate the sources That a problem has crept into your project. We'll discuss some of the techniques you can use when you find Well takes a top-notch revision control system. To err might be human, but to really handle the consequences It does Changes that should never have been Backing out a merge Protect yourself from escapedĬhanges What to do about sensitive changes that escape Finding the source of a bug Using the hg bisectĬommand Cleaning up after your search Tips for finding bugs effectively Give consistent input Automate as much as possible Check your results Beware interference between bugs Bracket your search lazily Table of Contents Erasing local history The accidental commit Rolling back a transaction The erroneous pull Rolling back is useless once you've pushed You can only roll back once Reverting the mistaken change File management errors Dealing with committed changes Backing out a changeset Backing out the tip changeset Backing out a non-tip change Always use the -merge option Gaining more control of the backout process Why hg backout works as
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |