bundles/org.eclipse.team.cvs.ui/help_contexts.xml

<?xml version="1.0" encoding="UTF-8"?>
<?NLS TYPE="org.eclipse.help.contexts"?>
<contexts>
   <context  id="new_cvs_connection_action_context" >
      <description>example</description>
	<topic label="Repositories - Concept" href="concepts/concepts-27c.htm"/>
 	<topic label="Repositories - Reference" href="reference/ref-47.htm"/> 
   	<topic label="CVS Repositories" href="reference/ref-47.htm"/>
	<topic label="Create a Repository Location" href="tasks/tasks-92.htm"/>
   	<topic label="Disconnecting from a Repository" href="tasks/tasks-94.htm"/>
   </context>
   
	<!-- ********************************** -->
 	<!-- TagSelectionDialog 				-->
 	<!-- ********************************** -->
	
	<context id="replace_tag_selection_dialog_context">
   		<description>This lets you replace the selected tag with another one, methinks ;-)
		</description>
   	</context>
   	
   	<context id="compare_tag_selection_dialog_context">
   		<description>This lets you compare the selected tag to another one, methinks ;-)
		</description>
   	</context>
   	
   	<context id="tag_remote_with_existing_dialog_context">
   		<description>You get here by selecting "Tag with existing" from the popup menu in the CVS repo view.
		</description>
   	</context>
   	
   	<context id="share_with_existing_tag_selection_dialog_context">
   		<description>Cor! No idea what this does.
		</description>
   	</context>
   	
   	<!-- ********************************** -->
 	<!-- TagAsVersionDialog 				-->
 	<!-- ********************************** -->
 	
 	<context id="tag_as_version_dialog_context">
   		<description>Tags the project with the version name you provide, methinks ;-)
		</description>
   	</context>
   	
   	<!-- ********************************** -->
 	<!-- WizardPages 						-->
 	<!-- ********************************** -->
 	
 	<context id="sharing_autoconnect_page_context">
   		<description>This should be obvious, methinks ;-)
		</description>
   	</context>
   	
   	<context id="sharing_select_repository_page_context">
   		<description>Here you can select an exisiting repository to use.
		</description>
   	</context>

 	<context id="sharing_new_repository_page_context">
   		<description>Here you can create a new repository to use for your project.
		</description>
   	</context>

 	<context id="sharing_module_page_context">
   		<description>Here you can decide whether to use the project name as the module name or give the module a different name.
		</description>
   	</context>

 	<context id="sharing_finish_page_context">
   		<description>All you need to do now is hit the 'Finish' button to share the project.
		</description>
   	</context>

 	<context id="patch_selection_page_context">
   		<description>Here you can select where you want to save the patch.
		</description>
   	</context>

 	<context id="patch_options_page_context">
   		<description>Here you can specify the kind of patch you would like, methinks ;-)
		</description>
   	</context>

 	<context id="keyword_substituton_selection_page_context">
   		<description>
		</description>
   	</context>

 	<context id="keyword_substituton_summary_page_context">
   		<description>
		</description>
   	</context>

 	<context id="keyword_substituton_shared_page_context">
   		<description>
		</description>
   	</context>

 	<context id="keyword_substituton_changed_page_context">
   		<description>
		</description>
   	</context>
   	
   	<!-- ********************************** -->
 	<!-- TeamMenuActions 					-->
 	<!-- ********************************** -->
	
	<context id="team_synchronize_action_context">
   		<description>Finds all differences between remote and local versions of the project.
		</description>
   	</context>
   	
   	<context id="team_synchronize_outgoing_action_context">
   		<description>Find all outgoing changes.
		</description>
   	</context>

 	<context id="team_commit_action_context">
   		<description>Updates the remote project with any changes that have been made locally.
		</description>
   	</context>

 	<context id="team_update_action_context">
   		<description>Updates the local project with any changes that have been made remotely.
		</description>
   	</context>

 	<context id="team_create_patch_action_context">
   		<description>Creates a patch that can be applied to the base project to bring it in sync with this copy.
		</description>
   	</context>

 	<context id="team_tag_as_version_action_context">
   		<description>Tags a project with a version name that you can provide.
		</description>
   	</context>

 	<context id="team_branch_action_context">
   		<description>Branch off a project into 2 streams.
		</description>
   	</context>

 	<context id="team_merge_action_context">
   		<description>Merge 2 disparate streams into one cohesive whole.
		</description>
   	</context>

 	<context id="team_set_keyword_mode_action_context">
   		<description>
		</description>
   	</context>

 	<context id="team_disconnect_action_context">
   		<description>Stop managing the project with this repo provider.
		</description>
   	</context>

 	<context id="team_add_action_context">
   		<description>Add this file to the repository
		</description>
   	</context>

 	<context id="team_ignore_action_context">
   		<description>Ignore this file for all remote sync operations.
		</description>
   	</context>

 	<!-- ********************************** -->
 	<!-- TagConfiguration 					-->
 	<!-- ********************************** -->
	
	<context  id="tag_configuration_overview" >
   		<description>Configure the branch and version tags that are shown in the workbench. By browsing remote CVS files for tags you can selectively choose, from the list of tags on each file, which tags should be remembered and which ones shouldn't. You can also select the files that will be automatically examined for tags.
		</description>
   	</context>
   
    <context  id="tag_configuration_refreshlist" >
      <description>This lists the files that are automatically examined for tags. By default, the .project file	is examined. But in some cases other files may have a more complete tag history and should be examined instead.
      </description>
   	</context>
   
   	<context  id="tag_configuration_refreshaction" >
      <description>This will fetch branch and version tags from the files that have been configured to be automatically searched for tags. If tags that you expected to see don't appear, try changing the list of files to examined via the tag configuration dialog.</description>
   	</context>

 	<!-- ********************************** -->
 	<!-- Dialogs					        -->
 	<!-- ********************************** -->
 	
 	<context id="release_comment_dialog_context">
       <description>Enter a comment to describe the contents of this release.</description>
    <!-- Below copied from old VCM
       <topic label="%context_ref_vcm_releasing" href="tasks/tasks-114.htm" />
    -->
    </context>
   	<context id="user_validation_dialog_context">
      <description>In this dialog, enter the appropriate information to log in to the repository.
      </description> 
    <!-- Below copied from old VCM
      <topic label="%context_ref_vcm_repositories_concept" href="concepts/concepts-27c.htm" /> 
      <topic label="%context_ref_vcm_create_repository_location" href="tasks/tasks-92.htm" /> 
      <topic label="%context_ref_vcm_repositories_reference" href="reference/ref-47.htm" />
    -->
    </context>
    <context id="tag_local_as_version_dialog_context">
      <description>Enter the name of the version tag to be applied to the revisions that exist locally.
      </description>
    </context>
    <context id="branch_dialog_context">
      <description>Enter the name of the branch tag to be applied to the revisions that exist locally.
      </description>
    </context>
    <context id="add_to_cvsignore_context">
    	<description>In this dialog choose how to add the selected resources to the .cvsignore files. For each resource to be ignored, a .cvsignore file will created in its parent directory containing the pattern specified in the dialog. This won't affect resources already under version control.
    	</description>
    </context>
    
 	<!-- ********************************** -->
 	<!-- Preference Pages 					-->
 	<!-- ********************************** -->
 	
 	<context  id="prune_empty_directories_pref" >
      <description>Enables pruning of empty directories on update and in the synchronization view. Although pruned directories aren't shown in the workbench there is actually still an empty directory in the repository.
      </description>
   	</context>
   	
   	<context  id="quietness_level_pref" >
      <description>Sets the amount of status information CVS prints for a command. In "Somewhat quiet" mode the printing of unimportant informational messages is supressed. The consideration of what is important depends on each command. In "Very quiet" mode all output except what is absolutely necessary to complete the command is suppressed. In "Very Quiet" mode, some cvs servers may not communicate important information about errors that have occured. You may want to consider using "Somewhat quiet" mode instead.
      </description>
   	</context>
   	
  	<context  id="compression_level_pref" >
      <description>Sets the compression level on communications with the server if it is supported by the server. Level 1 is minimal compression (very fast/low compression) and level 9 maximum compression (very slow/maximum compression).
      </description>
   	</context>

	<context  id="default_keywordmode_pref" >
      <description>Sets the default keyword substitution mode to use for text files.
      </description>
   	</context>
   	
	<context  id="comms_timeout_pref" >
      <description>Sets the amount of time in seconds to wait before timing out from a connection to the CVS server.
      </description>
   	</context>
   	
   	<context  id="consider_content_pref" >
      <description>Sets the default compare method for comparing and synchronizing CVS resources. By default timestamps are used to compare CVS files, and this is by far the fastest method. However, in some cases a more accurate comparison can be achieved by comparing file content. This setting can be toggled from within a compare editor or the synchronization view.
      </description>
   	</context>

	<context  id="markers_enabled_pref" >
      <description>Enables markers to be added to the task view for resources that have been locally removed but not committed and resources that have been locally added but not placed under CVS control.
      </description>
   	</context>
   	
	<context  id="replace_deletion_of_unmanaged_pref" >
      <description>Allows resources not under CVS control to be deleted when replacing with resources from the repository.
      </description>
   	</context>
   	
   	<!-- ********************************** -->
 	<!-- Views					            -->
 	<!-- ********************************** -->
 	
 	<context  id="console_view_context" >
      <description>This view shows the output of CVS operations.
      </description>
   	</context>
   	<context  id="repositories_view_context" >
      <description>This view allows the browsing of a remote CVS repository.
      </description>
   	</context>
   	<context  id="resource_history_view_context" >
      <description>This view shows the revision history of a resource under CVS control.
      </description>
   	</context>
   	<context  id="catchup_release_viewer_context" >
      <description>This view shows the incoming, outgoing and conflicting changes.
      </description>
   	</context>
   	   <context  id="compare_revisions_view_context" >
      <description>This view allows the comparision of the local copy of a file with the revisions from the respoitory.
      Actions availabel of a revision are "Get Contents" and "Get Revision". Although both replace the local file with the contents of the remote rvision, "Get Revision" will make the local file "sticky". This means that changes to the file cannot be committed back to the repository.
      </description>
   	</context>
   	
   	<!-- ********************************** -->
 	<!-- Actions					        -->
 	<!-- ********************************** -->
 	
 	<context  id="get_file_revision_action_context" >
      <description>Load the revision of the file into the workspace. The file will be "sticky" and the user will be unable to commit changes to the repository.
      </description>
   	</context>
 	<context  id="get_file_contents_action_context" >
      <description>Load the contents of the file into the workspace. The base revision of the local file will not change and the file will become dirty. Perform this action if you wich to revert to the contents of an older revision of the file.
      </description>
   	</context>
   
    <!-- ********************************** -->
 	<!-- Team Actions					    -->
 	<!-- ********************************** -->
 	
   	<context  id="team_commit_action_context" >
      <description>Commit outgoing changes to the respository
      </description>
   	</context>
   		
   	<!-- ********************************** -->
 	<!-- Sync Actions					    -->
 	<!-- ********************************** -->
 	
   	<context  id="sync_commit_action_context" >
      <description>Commit outgoing changes to the respository
      </description>
   	</context>

</contexts>