Hg tag -r $VER update $BRANCH >/dev/nullĮxample Usage: hg_tag. Hg merge -r $VER -tool internal:other >/dev/null #take only the 'tagging' version of hgtags Users aren't required to file messages in managed folders based on retention requirements. Separating MRM functionality from users' Inbox management and filing habits. VER=`hg id | sed 's#\(*\).*#\1#g'`Įcho_red "Directory contains unresolved files !" Allowing the user to assign personal tags to custom folders and individual items. I strongly recommend making a clone of your project before testing this script, in case it does not behave as you expect! #!/bin/bashĮcho " tags a version (current if not specified) in the 'tagging' branch."Įcho " Options are the 'hg tag' ones, plus" It can probably be improved, but it suits my needs. It merges the current branch in "tagging" branch, so it's easy to see the changeset tag was done from (it especially avoids long refreshes when switching branch). The little script below creates a branch "tagging" and puts tags in it. hgtags files on the heads of all branches. Moreover, tagging can be done from any branch, because Hg takes tags from the. I was used of SVN tagging which was done on a separate branch, which has the advantage not to change working branch history. Untagged items are mailbox items that dont already have a retention tag applied, either by inheritance from the folder in which theyre located or by the user. Tagging can burden a history graph very quickly. For my point of view, Hg tagging system is a bit messy because creating a tag changes the history and needs merging and committing even if no project file has changed.
0 Comments
Leave a Reply. |