$ patch -p1 < ~/new-feature.diff $ tf online % checkin
tf - Team Foundation Client
tf [/server:<server name or ip address>] [/login:<login credentials>] <command> [<command arguments>]
tf is a source control client for Microsoft Team Foundation Server.
Provide authentication credentials. If you don't specify a password you will be prompted for one. If you have gnome-keyring support enabled, TF will store the login credentials on your default keyring if configured to do so (see "Credentials.Save" configuration option below). The login username can be a domain account, in which case use the syntax "domain\\username".
Specify the Team Foundation Server. If you are within a mapped working folder, you don't need to specify the /server option, as this information is stored in the VersionControl.config cache file.
Pend an add on a file or files to the repository. To commit, you must issue a checkin command.
Show changeset details: committer, date, comment, and files changed. The changeset id is just an integer - no "C" prefix is required as in the diff command below.
Checkin pending changes in workspace. With no arguments, this command will checkin all files in your workspace, not just all files underneath your current working directory. Due to a limitation in Mono.GetOptions, the /comment parameter cannot include spaces. This will be fixed soon!
Checkout a file for editing. Command alias: edit.
With no arguments, displays current configuration. With 1 argument, deletes the configuration setting <key>. With 2 arguments, sets the value of <key> to <value>. See Configuration section below for more details on valid settings.
Pend a delete against a file or files from the repository. To commit, you must issue a checkin command.
Show pending changes as a diff. With /old, shows changes from current workspace to latest on the server as a diff. With /modified, shows changes to writable workspace files as a diff - another way to preview changes before using the online command. With a changeset id, like C12278, the command will show you a diff of the files changed in that changeset.
List files in specified server path. A way to explore the folders on the server without setting up a workspace and downloading the files.
Graphically explore a TF repository. Changeset view, directory view, and file view options. Control-C will copy currently selected path to the clipboard.
Update local repository copy with latest versions from the server. Think "cvs/svn update". Note: Files are initially set to read-only, until checked out with the checkout command.
Show builtin help. Optionally, specify a tf command for which to show detailed help. The /list option is primarily a helper for shell completion code.
Display changelog history for specified file. If you are looking for a git-log/svn log type function use this and add /recursive. Use /stopafter to limit the number of entries returned. Valid format specifiers include "brief" (the default), "detailed", and "byowner". The "detailed" format displays all files changed in a changeset and the "byowner" format summarizes the history by owner, showing how many changes each user committed.
Add a label or tag to an item.
Displays labels or tags. Can optionally filter by <labelname> and <ownername>.
Locks a file in the repository. Use /lock:none to remove the lock.
Shows known, deleted, modified, old, or unknown files under the given path. With no options, ls-files shows known files. /old option by default shows only files in your workspace which are out of date, not new files on the server you've not yet fetched. To show those files as well, use "/old /all". This behavior may change in future releases, based on user feedback.
Lists merge points in the history of the destination item. The destination item can either be expressed as a server item or a local item.
Finds all writable files and marks them as pending changes on the server. It also finds all unknown files and marks them as pending adds, missing files are marked as pending deletes. A great command to use if you apply a patch to a clean tfs-managed tree and want to pend the changes to the server for checkin. The /added, /modified, /deleted flags can be used to show just additions, just modifications, or just deletions respectively. These flags may be combined. With no flags, all changes are shown.
Show server permissions on a file. Command alias: permission.
Show detailed properties for each filename including server locks, encoding, last modified date, changeset id, and whether the file has a newer version on the server.
Rename a file or files in the repository.
Undo a changeset. Retrieves previous versions of all files modified in the selected changeset, then marks them as pending changes. NOTE: this command is only useful if no one else has changed the file since <changeset> was checked in. If a file has been modified by subsequent checkins and you rollback, all subsequent modifications will be lost!
Create or delete a shelveset. A shelveset is a way to store local changes on the server without checking them in.
Show shelvesets on the server. Use /owner:"*" and no name argument to view all shelvesets.
Show information about build configuration, cache settings, identity info, usage statistics, or registered server tools.
Show status of all pending changes in local workspace. Optional paths/filenames may be added to narrow the resulting output.
Delete all files not under version control. Use /preview to see what would be deleted.
Undo pending changes. With no filenames, undoes all pending changes.
Remove a label or tag from an item.
Manage workspaces.
List workspaces in server repository. Use /format:detailed for additional information. Specify a workspace name to filter results.
Manage working folders. With no arguments, print current working folder mappings. With a server path and local path, creates a new working folder mapping.
Displays the version of the program.
Displays the latest version of the specified file or files.
tf workspaces /server:10.2.10.2 /login:domain\\username,password /owner:"*" /computer:"*"
tf workspace /new "workspaceName;ownerName"
tf workfold "$/ProjectName" /home/username/src/project
tf get /recursive /home/username/src/project
tf workspace /delete workspaceName
tf ls-files /others %% add
You can execute multiple commands in sequence in a single run of TF, by separating the commands with %. Here's how you might checkin a patch with a single run of TF:
$ patch -p1 < ~/new-feature.diff $ tf online % checkin
If you'd like to pipe the output from the ls-files or diff (brief mode only) subcommands to the next subcommand in the chain use %% instead. This can be particularly useful with ls-files.
The TF client stores configuration settings in ~/.tf/TfClient.config.
The TF client will display a summary of pending changes and ask for confirmaton below committing changes to the server when set to "true". The default is "false". It's non-trivial to rollback a committed change, so this option is highly recommended.
The TF client will always checkout the latest version rather than the workspace version if this setting is set to "true". Note: this option only effects the checkout command, not the "online" command.
The TF client will store login credentials if this setting is set to "true". The default is "false".
A comma separated list of files to ignore. Currently, only the "online" command honors this setting. The wildcard characters and ? are supported. Example setting: ".dll,*.pdb".
The TF client defaults to setting all non-checked out files to readonly. Set this setting to "true" to make them read-write.
The TF client will default to updating all registered working folders if no folder arguments are given when running the subcommand "get". By enabling this option, the TF client will instead look for updates starting with the current working folder and subfolders (as needed). If you have lots of registered working folders but only actively track a few of these folders, the default behavior can become quite tedious.
The TF client does not default to preserving file modification times. By enabling this option, TF will set the modification time of any file subsequently fetched to the date of the last changeset in which the file was modified. Warning: this mode of operation can significantly slow down "tf get".
The TF client will automatically do recursive gets when set to "true". IMHO, this is far more useful than the default behavior.
The TF client defaults to brief output of history which does not include file level information. Set this setting to "true" to get file level history.
The TF client will default to the current working directory if not options are given when running the subcommand "history". The default behavior of the standard client is to require a path for all history queries. This option provides an optional and more sensible default.
The TF client will automatically do recursive history queries when set to "true". IMHO, this is far more useful than the default behavior.
The TF client defaults to showing the last 255 checkins in history output. Set this option to an integer to change the default.
The TF client will automatically do recursive merge queries when set to "true". IMHO, this is far more useful than the default behavior.
The TF client will automatically do a recursive online command when set to "true". IMHO, this is far more useful than the default behavior for clean trees. Not as helpful for trees littered with build output files.
If the TF client cannot determine the server to connect to, first from the "/server:" option, and second the workspace cache, then it will use the Server.Default setting if non-null.
If the TF client cannot determine the active workspace, first from the "/workspace:" option, and second the workspace cache, then it will use the Workspace.Default setting if non-null.
The TF client keeps a cache of workspaces and folder mappings in ~/.tf/Cache/VersionControl.config. Here's a sample file:
The contents of the cache can be seen with the tf cache command.
<VersionControlServer>
<Servers>
<ServerInfo uri="http://10.2.1.2:8080/">
<WorkspaceInfo name="neo" ownerName="DOMAIN\USER" computer="MYBOX" comment="" LastSavedCheckinTimeStamp="4/26/2007 11:55:50 PM">
<MappedPaths>
<MappedPath path="/home/jreed/Source/xyz-project" />
<MappedPath path="/home/jreed/Source/abc-project" />
</MappedPaths>
</WorkspaceInfo>
</ServerInfo>
</Servers>
</VersionControlServer>
TFS doesn't have built in support for tracking file attributes, for example, whether the file is executable or not. The TF client included in this package makes use of libmagic to determine whether a file should be marked executable or not.
http://groups.google.com/group/opentf http://msdn2.microsoft.com/en-us/library/bb130146(VS.80).aspx http://msdn2.microsoft.com/en-us/teamsystem/default.aspx http://msdn2.microsoft.com/en-us/cc31bk2e(VS.80).aspx
Written by Joel Reed <joelwreed@gmail.com>
Documentation by Joel Reed <joelwreed@gmail.com>