56     Add the given files to the repository.  Note that this just schedules the

    56     Schedule files to be version controlled and added to the repository.

    57     files for addition at the next hg commit time.

    57     

    58     The files get effectively added to the repository at the next commit.

    60     Add all new files and remove all missing files from the repository.  New

    61     Add all new files and remove all missing files from the repository.

    61     files are ignored if they match any of the patterns in .hgignore

    62     

    63     New files are ignored if they match any of the patterns in .hgignore. As

    64     with add, the effects of this command take place at the next commit.

    64     List the files with each line showing the revision id responsible

    67     List changes in files, showing the revision id responsible for each line

    65     for that line.

    68     

    66 

    69     This command is useful to discover who did a change or when a change took

    70     place.

    71     

    74     Output the given revision or tip of the specified file to stdout.

    79     Output to stdout the given revision for the specified file.

    80 

    81     In case no revision is given, then the tip is used.

    77     Create a new copy of an existing repository.

    84     Create a copy of an existing repository in a new directory.

    85 

    86     If the destination directory is specified, but doesn't exist, it is

    87     created. If no destination directory is specified, it defaults to the

    88     current directory.

    89 

    90     The source is added to the new copy's .hg/hgrc file to be used in

    91     future pulls.

    92 

    93     For speed and storage size, hardlinks are used to do the copy whenever

    94     the specified source and destination are on the same filesystem.

    95 

    96     options:

    97     -U, --no-update   do not update the new working directory

    98 

    99 commit [-A -t -l <file> -t <text> -u <user> -d <datecode>] [files...]::

   100     Incorporate changes from given files into the repository.

   101     

   102     If a list of files is ommited, all of the working dir files will

   103     be commited.

   104     

   105     The EDITOR environment variable is used to bring up an editor to add

   106     a commit comment.

   107 

   108     Options:

   109 

   110     -A, --addremove       run addremove during commit

   111     -t, --text <text>     use <text> as commit message

   112     -l, --logfile <file>  show the commit message for the given file

   113     -d, --date <datecode> record datecode as commit date

   114     -u, --user <user>     record user as commiter

   115 

   116     aliases: ci

   117 

   118 copy <source> <dest>::

   119     Mark <dest> file as a copy or rename of a <source> one

   120     

   121     This command takes effect for the next commit.

   122 

   123 diff [-r revision] [-r revision] [files ...]::

   124     Show differences between revisions for the specified files.

   125     

   126     Differences between files are shown using the unified diff format.

   127     

   128     When two revision arguments are given, then changes are shown between

   129     such revisions. If only one revision is specified then that revision is

   130     compared to the tip, and, when no revisions are specified, the working

   131     directory files are compared to the tip.

   132 

   133 export [revision]::

   134     Print the changeset header and diffs for a particular revision.

   135 

   136     The information shown in the changeset header is: author, changeset hash,

   137     parent and commit comment.

   138 

   139 forget [files]::

   140     Undo an 'hg add' scheduled for the next commit.

   141 

   142 heads::

   143     Show all repository head changesets.

   144     

   145     Repository "heads" are changesets that don't have children changesets.

   146     They are where development generally takes place and are the usual targets

   147     for update and merge operations.

   148 

   149 history::

   150     Print a log of the revision history of the repository.

   151     

   152     By default this command outputs: changeset id and hash, tags, parents,

   153     user, date and time, and a summary for each commit.

   154     The -v switch adds some more detail, such as changed files, manifest

   155     hashes or message signatures.

   156 

   157     To display the history of a given file, see the log command.

   158 

   159 identify::

   160     Print a short summary of the current state of the repo.

   161     

   162     This summary identifies the repository state using one or two parent

   163     hash identifiers, followed by a "+" if there are uncommitted changes

   164     in the working directory, followed by a list of tags for this revision.

   165 

   166     aliases: id

   167 

   168 import [-p <n> -b <base> -q] <patches>::

   169     Import a list of patches and commit them individually.

   170 

   171     options:

   172     -p, --strip <n>   directory strip option for patch. This has the same

   173                       meaning as the correnponding patch option

   174     -b <path>         base directory to read patches from

   175 

   176     aliases: patch

   177 

   159     Print the indicated revision of the manifest (list of version controlled

   204     Print a list of version controlled files for the given revision.

   160     files).

   205 

   206     The manifest is the list of files being version controlled. If no revision

   207     is given then the tip is used.

   166     Pull any changes from the specified repository to the repository in the

   213     Pull any changes from a repository to the current directory's one.

   167     current directory.

   214 

   215     Pulling is a fundamental operation in a distributed version control system,

   216     as it eases handling changes from different branches, both local and

   217     remote, into the current repository. 

   173     Push changes from the local repository to the specified

   223     Push changes from the local repository to the given destination.

   174     destination. If the destination is local, this is identical to a

   224     

   175     a pull in that directory from the current directory.

   225     This is the symmetrical operation for pull. It helps to move changes from

   226     the current repository to a different one. If the destination is local

   227     this is identical to a pull in that directory from the current one.

   185     Primarily useful for importing from other SCMs.

   237     Lowlevel commit, for use in helper scripts.

   238     

   239     This command is not intended to be used by normal users, as it is

   240     primarily useful for importing from other SCMs.

   188     Recover from an interrupted commit or pull. This should only be

   243     Recover from an interrupted commit or pull.

   189     necessary when Mercurial suggests it.

   244     

   245     This command tries to fix the repository status after an interrupted

   246     operation. It should only be necessary when Mercurial suggests it.

   192     Schedule the indicated files for removal from the repository at the next

   249     Schedule the indicated files for removal from the repository.

   193     commit.

   250     

   251     This command shedules the files to be removed, but the actual removing

   252     takes place at the next commit.

   218     Add a tag <name> to the specified revision or the tip.

   279     Name a particular revision using <name>.

   219 

   280     

   281     Tags are used to name particular revisions of the repository and are

   282     very useful to compare different revision, to go back to significant

   283     earlier versions or to set special branch points, as releases, etc.

   284     

   285     If no revision is given as argument the tip is used.

   286 

   287     This tags are versioned, and kept along with the repository metadata. But

   288     Mercurial has support for other type of tags that can be used locally for

   289     convenience and that are created adding lines with a changeset hash value

   290     and a name or names to name the revision in a .hgtags file

   291     

   235     Update or merge the working directory to a specified revision.

   309     Bring the working directory to the state of a given revision.

   236 

   310 

   237     If there are no outstanding changes in the working directory and

   311     After running this command the current directory will have the contents

   238     there is a linear relationship between the current version and the

   312     of the specified revision.

   239     requested version, the result is the requested version.

   313     

   240 

   314     If there were outstanding changes in the current directory and a merge

   241     Otherwise the result is a merge between the contents of the

   315     would be needed, the -m option can be used to merge those changes with

   242     current working directory and the requested version. Files that

   316     the target revision. Without the -m or --merge option, no merge

   243     changed between either parent are marked as changed for the next

   317     will happen.

   244     commit and a commit must be performed before any further updates

   318     

   245     are allowed. Merging will not be performed without the -m flag.

   319     The -C or --clean option must be used in case a pristine version is

   246 

   320     desired. In this case, existing changes will be discarded and lost. If

   247     The -C switch will tell Mercurial to forcibly update to the

   321     these changes should be kept, then a commit prior updating, or a merge

   248     specified version, adding, removing, and overwriting locally

   322     is due.

   249     changed fils as necessary.

   323     

   250