Changes between Version 16 and Version 17 of TracRepositories

Timestamp:

Jan 30, 2015, 12:23:41 AM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes

TracRepositories

@@ -1 @@
-= Trac Repositories =
+= Trac Repositories
 
 == Official Subversion repository
@@ -7 +7 @@
  http://svn.edgewall.org/repos/trac/
 
-In addition, see TracDev/SubmittingPatches for instructions to create and submit patches.
+In addition, see TracDev/SubmittingPatches for instructions on how to create and submit patches.
 
 Example:
@@ -25 +25 @@
 == Official mirrors    #OfficialMirrors
 
-We now have official DVCS mirrors of the Subversion trunk and maintenance branches which are updated after every commit. For anything else than small fixes, it is more 
-convenient to maintain your changes  in your own repositories as it'll be easier to maintain them as the code base continues to evolve upstream (rebase, MQ, etc.).
+We now have official DVCS mirrors of the Subversion trunk and maintenance branches which are updated after every commit. For anything other than small fixes, it is more convenient to maintain your changes in your own repositories. That way, it will be easier to maintain them as the code base continues to evolve upstream (rebase, MQ, etc.).
 
 === Mercurial mirror on bitbucket.org
@@ -32 +31 @@
  http://bitbucket.org/edgewall/trac
 
-You can either register for a BitBucket account and then "Fork" the above repository, which will create your own `trac` repository  under your account.
+You can register for a BitBucket account and then "Fork" the above repository, which will create your own `trac` repository  under your account.
 
 Alternatively, you can directly clone the edgewall/trac repository and submit your changes via patches attached to the relevant tickets.
@@ -40 +39 @@
 }}}
 
-The mirror contains `trunk`, all `0.x-stable` branches since 0.7 as well as the corresponding tags. To facilitate linking the Mercurial changesets with the corresponding changesets in Subversion, you may want to install the [http://rc.c-space.org/hg/HgSvnUtils/ HgSvnUtils] Mercurial extension (maintained by RemyBlank). It automatically adds "virtual" tags for every changeset converted from Subversion, containing the SVN revision number:
+The mirror contains `trunk`, all `0.x-stable` branches since Trac 0.7 as well as the corresponding tags. To facilitate linking the Mercurial changesets with the corresponding changesets in Subversion, you may want to install the [http://rc.c-space.org/hg/HgSvnUtils/ HgSvnUtils] Mercurial extension (maintained by RemyBlank). It automatically adds "virtual" tags for every changeset converted from Subversion, containing the SVN revision number:
 {{{
 $ hg glog
@@ -60 +59 @@
 }}}
 
-This allows easily updating to a given SVN revision, or comparing to a given SVN revision:
+This allows easy updating to a given SVN revision, or a comparison to a given SVN revision:
 
 {{{
@@ -80 +79 @@
 }}}
 
-Note that when working with mixed working copies on Windows (i.e. a Subversion working copy which also contains a cloned `.hg` repository at its root), it can be useful to activate the `eol` Mercurial extension (see r9979 for details), otherwise after an `svn update` the files can appear to be modified to `hg` due to different line endings. This is because the Mercurial mirror has been created on Linux, therefore all the files are stored in LF mode, in the repository.
+Note that when working with mixed working copies on Windows (i.e. a Subversion working copy which also contains a cloned `.hg` repository at its root), it can be useful to activate the `eol` Mercurial extension (see r9979 for details). Otherwise, after an `svn update`, the files can appear to be modified to `hg` due to different line endings. This is because the Mercurial mirror has been created on Linux, therefore all the files are stored in LF mode in the repository.
 
 === Git mirror on github.com