Saving a password for a repository (if done at all) probably goes inside that repos. Something like setting your username is probably best done only for you, in your %USERPROFILE%\Mercurial.ini. Something like enabling an extension might be best done system global in C:\Mercurial. ((repository root))\.hg\hgrc - If you choose to create this whatever you put in it affects only the repository in which you placed it %USERPROFILE%\Mercurial.ini - If you choose to create this whatever you put in it affects only you, but in every repo with with you interact They're places you can put configuration information depending on what scope you want it to have:Ĭ:\Mercurial\Mercurial.ini - If you choose to create this whatever you put in it affects all users on the systme Disable it on the peril of aggravating the whole OOo developer community.They're not supposed to be automatically created. This is one of the hooks provided by 'win32text'. The 'win32text' extension is strongly suggested for all OOo developers who work on windows at least occasionally, it provides a hook which prevents you from committing files with CR/LF in them. The 'mq' extension is required if you want to use the 'cws fetch' tool since it makes use of 'hg strip' which is part of the 'mq' extension. Mercurial supports a huge number of useful extensions, many of them come bundled. Be sure to use a compressed ssh connection ( -C). Publishing changes on hg. requires SSH access, which is configured here. OOo domain developers can create "child workspaces", which are effectively public feature branches. If you are absolutely not comfortable with disclosing your real name it's possible to use a pseudonym or just your account name instead, but be reasonable. It must always be possible to relate a contribution with an OOo account, the contribution will be rejected otherwise. It's possible to use other email addresses than the OOo one, but in this case please add your OOo account in square braces. Set this entry to identify yourself as author, common usage is to use your name and the OOo email address here. The author tag of a changeset is set on commit, and becomes part of the history. Let's examine this configuration file entry for entry: # Enabling this hook is strongly suggested for OOo development. # Reject commits which would introduce windows-style CR/LF. # Enables the bundled win32text extension.
# Required if 'cws fetch' is used to fetch a CWS.
# Domain developers only: OOo ssh authentication for pushing # The user name will appear as author tag on commits. The most interesting one is the user specific configuration file in $HOME/.hgrc. Mercurial can be configured via system, user and repository configure files. Please see Submitting Your Certificate (Public Key). We will continue to use IssueZilla for managing and tracking key additions and changes. If you are a new domain developer please create a new issue, attach your public key to it and and add it as a dependency to issue 94002. Ssh-keygen -t dsa -f ~/.ssh/id_dsa_ooo_svnĪll existing public keys for SVN usage have been migrated for Mercurial use as well.
If you want a dedicated identity for just OOo SVN usage, generate a specially named key pair Note that SSH keys created between September 2006 and May 2008 on Debian or Debian derived systems like Ubuntu may be insecure. Per default the public key is named $HOME/.ssh/id_dsa.pub. You'll be asked for pass phrase which protects your private key. On Unix or Windows/cygwin a SSH identity (private/public key pair) is generated with: Mercurial is a distributed SCM, there are other ways to contribute your changes without having write access to this server. If you are not a domain developer or do not plan to publish your changes via this way to the OOo community just skip this section. If your cygwin hg complains about: "*** fatal error - could not load shell32, Win32 error 487" use TortoiseHg instead.ĭomain developers can publish their changes on hg. Some cygwin versions exhibit a bug which affects hg and other tools.
0 kommentar(er)
