Edgewall Software

Changes between Version 9 and Version 10 of TracRepositories


Ignore:
Timestamp:
Jul 2, 2010, 9:28:44 AM (14 years ago)
Author:
Christian Boos
Comment:

#9235 completed

Legend:

Unmodified
Added
Removed
Modified
  • TracRepositories

    v9 v10  
    11= Trac Subversion Repository =
    22
    3 Everyone has read access to the Trac Subversion repository located at http://svn.edgewall.org/repos/trac/. In addition, see [wiki:TracDev/SubmittingPatches] for instructions to download the latest source and create and submit patches.
     3Everyone has read access to the Trac Subversion repository located at:
     4
     5 http://svn.edgewall.org/repos/trac/
     6
     7In addition, see TracDev/SubmittingPatches for instructions to create and submit patches.
    48
    59Example:
     
    1115}}}
    1216
    13 Please send patches to the MailingList for review and merging. If you think you should have write-permission to the repository, please contact JonasBorgstrom directly: he will possibly give you an account and a password with which you will be able to commit to the repository (thru https://svn.edgewall.org/repos/trac/).
     17Please attach patches to the appropriate ticket for review and merging.
    1418
    15 A public (unofficial) [http://www.selenic.com/mercurial/ Mercurial] mirror is available [http://hg.xavamedia.nl/trac/ here]. This is useful if you want to keep track of development versions and/or rebase some of your own changes against it using Mercurial Queues (or to help develop patches against official Trac trunk).
    16 See also #9235.
     19If you think you should have write-permission to the repository, please contact JonasBorgstrom directly: he will possibly give you an account and a password with which you will be able to commit to the repository (in that case, use HTTPS for the checkout, i.e. https://svn.edgewall.org/repos/trac/).
     20
     21== Mirrors
     22
     23We 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
     24convenient 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.).
     25
     26=== Mercurial mirror on bitbucket.org
     27
     28 http://bitbucket.org/edgewall/trac
     29
     30You can either register for a BitBucket account and then "Fork" the above repository, which will create your own `trac` repository  under your account.
     31
     32Alternatively, you can directly clone the edgewall/trac repository and submit your changes via patches attached to the relevant tickets.
     33
     34{{{
     35hg clone http://bitbucket.org/edgewall/trac
     36}}}
     37
     38=== Git mirror on github.com
     39
     40 http://github.com/edgewall/trac
     41
     42You can either register for a GitHub account and then "Fork" the above repository, which will create your own `trac` repository  under your account.
     43
     44Alternatively, you can directly clone the edgewall/trac repository and submit your changes via patches attached to the relevant tickets.
     45
     46{{{
     47git clone http://github.com/edgewall/trac.git
     48}}}
    1749
    1850----