archive-fr.com » FR » C » COREDUMP.FR

Total: 368

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • reporter: urls.py@d94facfd5bc6
    Rasneur vrasneur free fr 6 7 This program is free software you can redistribute it and or modify 8 it under the terms of the GNU Affero General Public License as published by 9 the Free Software Foundation version 3 only 10 11 This program is distributed in the hope that it will be useful 12 but WITHOUT ANY WARRANTY without even the implied warranty of 13 MERCHANTABILITY or FITNESS

    Original URL path: http://vrasneur.coredump.fr/reporter/file/d94facfd5bc6/urls.py (2015-02-06)
    Open archived version from archive


  • reporter: File revisions
    port to django 1 0 beta file diff annotate Wed 27 Aug 2008 00 33 15 0200 minor fixes file diff annotate Mon 25 Aug 2008 00 11 48 0200 small fixes file diff annotate Sun 24 Aug 2008 21 49 20 0200 table for time spent result is dynamically sortable now file diff annotate Sat 23 Aug 2008 19 37 32 0200 cleaner url dispatching file diff annotate Sat

    Original URL path: http://vrasneur.coredump.fr/reporter/log/d94facfd5bc6/urls.py (2015-02-06)
    Open archived version from archive

  • reporter: urls.py@d94facfd5bc6 (annotated)
    redistribute it and or modify vrasneur 106 8 it under the terms of the GNU Affero General Public License as published by vrasneur 106 9 the Free Software Foundation version 3 only vrasneur 106 10 vrasneur 106 11 This program is distributed in the hope that it will be useful vrasneur 106 12 but WITHOUT ANY WARRANTY without even the implied warranty of vrasneur 106 13 MERCHANTABILITY or FITNESS FOR

    Original URL path: http://vrasneur.coredump.fr/reporter/annotate/d94facfd5bc6/urls.py (2015-02-06)
    Open archived version from archive

  • reporter: Branches
    sendmail to send messages charsets Optional Comma separated list of character sets considered convenient for recipients Addresses headers and parts not containing patches of outgoing messages will be encoded in the first character set to which conversion from local encoding HGENCODING ui fallbackencoding succeeds If correct conversion fails the text in question is sent as is Defaults to empty explicit list Order of outgoing email character sets 1 us ascii always first regardless of settings 2 email charsets in order given by user 3 ui fallbackencoding if not in email charsets 4 HGENCODING if not in email charsets 5 utf 8 always last regardless of settings Email example email from Joseph User joe user example com method usr sbin sendmail charsets for western Europeans us ascii utf 8 omitted as they are tried first and last charsets iso 8859 1 iso 8859 15 windows 1252 extensions Mercurial has an extension mechanism for adding new features To enable an extension create an entry for it in this section If you know that the extension is already in Python s search path you can give the name of the module followed by with nothing after the Otherwise give a name that you choose followed by followed by the path to the py file including the file name extension that defines the extension To explicitly disable an extension that is enabled in an hgrc of broader scope prepend its path with as in foo ext path or foo when path is not supplied Example for hgrc extensions the mq extension will get loaded from Mercurial s path mq this extension will get loaded from the file specified myfeature hgext myfeature py format usestore Enable or disable the store repository format which improves compatibility with systems that fold case or otherwise mangle filenames Enabled by default Disabling this option will allow you to store longer filenames in some situations at the expense of compatibility and ensures that the on disk format of newly created repositories will be compatible with Mercurial before version 0 9 4 usefncache Enable or disable the fncache repository format which enhances the store repository format which has to be enabled to use fncache to allow longer filenames and avoids using Windows reserved names e g nul Enabled by default Disabling this option ensures that the on disk format of newly created repositories will be compatible with Mercurial before version 1 1 dotencode Enable or disable the dotencode repository format which enhances the fncache repository format which has to be enabled to use dotencode to avoid issues with filenames starting with on Mac OS X and spaces on Windows Enabled by default Disabling this option ensures that the on disk format of newly created repositories will be compatible with Mercurial before version 1 7 graph Web graph view configuration This section let you change graph elements display properties by branches for instance to make the default branch stand out Each line has the following format branch argument value where branch is the name of the branch being customized Example graph 2px width default width 2 red color default color FF0000 Supported arguments width Set branch edges width in pixels color Set branch edges color in hexadecimal RGB notation hooks Commands or Python functions that get automatically executed by various actions such as starting or finishing a commit Multiple hooks can be run for the same action by appending a suffix to the action Overriding a site wide hook can be done by changing its value or setting it to an empty string Hooks can be prioritized by adding a prefix of priority to the hook name on a new line and setting the priority The default priority is 0 if not specified Example hg hgrc hooks update working directory after adding changesets changegroup update hg update do not use the site wide hook incoming incoming email my email hook incoming autobuild my build hook force autobuild hook to run before other incoming hooks priority incoming autobuild 1 Most hooks are run with environment variables set that give useful additional information For each hook below the environment variables it is passed are listed with names of the form HG foo changegroup Run after a changegroup has been added via push pull or unbundle ID of the first new changeset is in HG NODE URL from which changes came is in HG URL commit Run after a changeset has been created in the local repository ID of the newly created changeset is in HG NODE Parent changeset IDs are in HG PARENT1 and HG PARENT2 incoming Run after a changeset has been pulled pushed or unbundled into the local repository The ID of the newly arrived changeset is in HG NODE URL that was source of changes came is in HG URL outgoing Run after sending changes from local repository to another ID of first changeset sent is in HG NODE Source of operation is in HG SOURCE see preoutgoing hook for description post command Run after successful invocations of the associated command The contents of the command line are passed as HG ARGS and the result code in HG RESULT Parsed command line arguments are passed as HG PATS and HG OPTS These contain string representations of the python data internally passed to command HG OPTS is a dictionary of options with unspecified options set to their defaults HG PATS is a list of arguments Hook failure is ignored pre command Run before executing the associated command The contents of the command line are passed as HG ARGS Parsed command line arguments are passed as HG PATS and HG OPTS These contain string representations of the data internally passed to command HG OPTS is a dictionary of options with unspecified options set to their defaults HG PATS is a list of arguments If the hook returns failure the command doesn t execute and Mercurial returns the failure code prechangegroup Run before a changegroup is added via push pull or unbundle Exit status 0 allows the changegroup to proceed Non zero status will cause the push pull or unbundle to fail URL from which changes will come is in HG URL precommit Run before starting a local commit Exit status 0 allows the commit to proceed Non zero status will cause the commit to fail Parent changeset IDs are in HG PARENT1 and HG PARENT2 prelistkeys Run before listing pushkeys like bookmarks in the repository Non zero status will cause failure The key namespace is in HG NAMESPACE preoutgoing Run before collecting changes to send from the local repository to another Non zero status will cause failure This lets you prevent pull over HTTP or SSH Also prevents against local pull push outbound or bundle commands but not effective since you can just copy files instead then Source of operation is in HG SOURCE If serve operation is happening on behalf of remote SSH or HTTP repository If push pull or bundle operation is happening on behalf of repository on same system prepushkey Run before a pushkey like a bookmark is added to the repository Non zero status will cause the key to be rejected The key namespace is in HG NAMESPACE the key is in HG KEY the old value if any is in HG OLD and the new value is in HG NEW pretag Run before creating a tag Exit status 0 allows the tag to be created Non zero status will cause the tag to fail ID of changeset to tag is in HG NODE Name of tag is in HG TAG Tag is local if HG LOCAL 1 in repository if HG LOCAL 0 pretxnchangegroup Run after a changegroup has been added via push pull or unbundle but before the transaction has been committed Changegroup is visible to hook program This lets you validate incoming changes before accepting them Passed the ID of the first new changeset in HG NODE Exit status 0 allows the transaction to commit Non zero status will cause the transaction to be rolled back and the push pull or unbundle will fail URL that was source of changes is in HG URL pretxncommit Run after a changeset has been created but the transaction not yet committed Changeset is visible to hook program This lets you validate commit message and changes Exit status 0 allows the commit to proceed Non zero status will cause the transaction to be rolled back ID of changeset is in HG NODE Parent changeset IDs are in HG PARENT1 and HG PARENT2 preupdate Run before updating the working directory Exit status 0 allows the update to proceed Non zero status will prevent the update Changeset ID of first new parent is in HG PARENT1 If merge ID of second new parent is in HG PARENT2 listkeys Run after listing pushkeys like bookmarks in the repository The key namespace is in HG NAMESPACE HG VALUES is a dictionary containing the keys and values pushkey Run after a pushkey like a bookmark is added to the repository The key namespace is in HG NAMESPACE the key is in HG KEY the old value if any is in HG OLD and the new value is in HG NEW tag Run after a tag is created ID of tagged changeset is in HG NODE Name of tag is in HG TAG Tag is local if HG LOCAL 1 in repository if HG LOCAL 0 update Run after updating the working directory Changeset ID of first new parent is in HG PARENT1 If merge ID of second new parent is in HG PARENT2 If the update succeeded HG ERROR 0 If the update failed e g because conflicts not resolved HG ERROR 1 Note It is generally better to use standard hooks rather than the generic pre and post command hooks as they are guaranteed to be called in the appropriate contexts for influencing transactions Also hooks like commit will be called in all contexts that generate a commit e g tag and not just the commit command Note Environment variables with empty values may not be passed to hooks on platforms such as Windows As an example HG PARENT2 will have an empty value under Unix like platforms for non merge changesets while it will not be available at all under Windows The syntax for Python hooks is as follows hookname python modulename submodule callable hookname python path to python module py callable Python hooks are run within the Mercurial process Each hook is called with at least three keyword arguments a ui object keyword ui a repository object keyword repo and a hooktype keyword that tells what kind of hook is used Arguments listed as environment variables above are passed as keyword arguments with no HG prefix and names in lower case If a Python hook returns a true value or raises an exception this is treated as a failure hostfingerprints Fingerprints of the certificates of known HTTPS servers A HTTPS connection to a server with a fingerprint configured here will only succeed if the servers certificate matches the fingerprint This is very similar to how ssh known hosts works The fingerprint is the SHA 1 hash value of the DER encoded certificate The CA chain and web cacerts is not used for servers with a fingerprint For example hostfingerprints hg intevation org 38 76 52 7c 87 26 9a 8f 4a f8 d3 de 08 45 3b ea d6 4b ee cc This feature is only supported when using Python 2 6 or later http proxy Used to access web based Mercurial repositories through a HTTP proxy host Host name and optional port of the proxy server for example myproxy 8000 no Optional Comma separated list of host names that should bypass the proxy passwd Optional Password to authenticate with at the proxy server user Optional User name to authenticate with at the proxy server always Optional Always use the proxy even for localhost and any entries in http proxy no True or False Default False merge patterns This section specifies merge tools to associate with particular file patterns Tools matched here will take precedence over the default merge tool Patterns are globs by default rooted at the repository root Example merge patterns c kdiff3 jpg myimgmerge merge tools This section configures external merge tools to use for file level merges Example hgrc merge tools Override stock tool location kdiff3 executable bin kdiff3 Specify command line kdiff3 args base local other o output Give higher priority kdiff3 priority 1 Define new tool myHtmlTool args m local other base output myHtmlTool regkey Software FooSoftware HtmlMerge myHtmlTool priority 1 Supported arguments priority The priority in which to evaluate this tool Default 0 executable Either just the name of the executable or its pathname On Windows the path can use environment variables with ProgramFiles syntax Default the tool name args The arguments to pass to the tool executable You can refer to the files being merged as well as the output file through these variables base local other output Default local base other premerge Attempt to run internal non interactive 3 way merge tool before launching external tool Options are true false or keep to leave markers in the file if the premerge fails Default True binary This tool can merge binary files Defaults to False unless tool was selected by file pattern match symlink This tool can merge symlinks Defaults to False even if tool was selected by file pattern match check A list of merge success checking options changed Ask whether merge was successful when the merged file shows no changes conflicts Check whether there are conflicts even though the tool reported success prompt Always prompt for merge success regardless of success reported by tool checkchanged True is equivalent to check changed Default False checkconflicts True is equivalent to check conflicts Default False fixeol Attempt to fix up EOL changes caused by the merge tool Default False gui This tool requires a graphical interface to run Default False regkey Windows registry key which describes install location of this tool Mercurial will search for this key first under HKEY CURRENT USER and then under HKEY LOCAL MACHINE Default None regkeyalt An alternate Windows registry key to try if the first key is not found The alternate key uses the same regname and regappend semantics of the primary key The most common use for this key is to search for 32bit applications on 64bit operating systems Default None regname Name of value to read from specified registry key Defaults to the unnamed default value regappend String to append to the value read from the registry typically the executable name of the tool Default None patch Settings used when applying patches for instance through the import command or with Mercurial Queues extension eol When set to strict patch content and patched files end of lines are preserved When set to lf or crlf both files end of lines are ignored when patching and the result line endings are normalized to either LF Unix or CRLF Windows When set to auto end of lines are again ignored while patching but line endings in patched files are normalized to their original setting on a per file basis If target file does not exist or has no end of line patch line endings are preserved Default strict paths Assigns symbolic names to repositories The left side is the symbolic name and the right gives the directory or URL that is the location of the repository Default paths can be declared by setting the following entries default Directory or URL to use when pulling if no source is specified Default is set to repository from which the current repository was cloned default push Optional Directory or URL to use when pushing if no destination is specified phases Specifies default handling of phases See hg help phases for more information about working with phases publish Controls draft phase behavior when working as a server When true pushed changesets are set to public in both client and server and pulled or cloned changesets are set to public in the client Default True new commit Phase of newly created commits Default draft profiling Specifies profiling type format and file output Two profilers are supported an instrumenting profiler named ls and a sampling profiler named stat In this section description profiling data stands for the raw data collected during profiling while profiling report stands for a statistical text report generated from the profiling data The profiling is done using lsprof type The type of profiler to use Default ls ls Use Python s built in instrumenting profiler This profiler works on all platforms but each line number it reports is the first line of a function This restriction makes it difficult to identify the expensive parts of a non trivial function stat Use a third party statistical profiler statprof This profiler currently runs only on Unix systems and is most useful for profiling commands that run for longer than about 0 1 seconds format Profiling format Specific to the ls instrumenting profiler Default text text Generate a profiling report When saving to a file it should be noted that only the report is saved and the profiling data is not kept kcachegrind Format profiling data for kcachegrind use when saving to a file the generated file can directly be loaded into kcachegrind frequency Sampling frequency Specific to the stat sampling profiler Default 1000 output File path where profiling data or report should be saved If the file exists it is replaced Default None data is printed on stderr revsetalias Alias definitions for revsets See hg help revsets for details server Controls generic server settings uncompressed Whether to allow clients to clone a repository using the uncompressed streaming protocol This transfers about 40 more data than a regular clone but uses less memory and CPU on both server and client Over a LAN 100 Mbps or better or a very fast WAN an uncompressed streaming

    Original URL path: http://vrasneur.coredump.fr/reporter/help/config (2015-02-06)
    Open archived version from archive

  • reporter: Branches
    for 0000 Dec 6 midnight 13 18 today assumed 3 39 3 39AM assumed 3 39pm 15 39 2006 12 06 13 18 29 ISO 8601 format 2006 12 6 13 18 2006 12 6 12 6 12 6 12 6 6 Dec 6 2006 Lastly there is Mercurial s internal format 1165432709 0 Wed Dec 6 13 18 29 2006 UTC This is the internal representation format for dates

    Original URL path: http://vrasneur.coredump.fr/reporter/help/dates (2015-02-06)
    Open archived version from archive

  • reporter: Branches
    supports the extended diff format from the git VCS which addresses these limitations The git diff format is not produced by default because a few widespread tools still do not understand this format This means that when generating diffs from a Mercurial repository e g with hg export you should be careful about things like file copies and renames or other things mentioned above because when applying a standard diff

    Original URL path: http://vrasneur.coredump.fr/reporter/help/diffs (2015-02-06)
    Open archived version from archive

  • reporter: Branches
    strict which causes Mercurial to abort if it can t map a character Other settings include replace which replaces unknown characters and ignore which drops them This setting can be overridden with the encodingmode command line option HGENCODINGAMBIGUOUS This sets Mercurial s behavior for handling characters with ambiguous widths like accented Latin characters with East Asian fonts By default Mercurial assumes ambiguous characters are narrow set this variable to wide if such characters cause formatting problems HGMERGE An executable to use for resolving merge conflicts The program will be executed with three arguments local file remote file ancestor file deprecated use configuration file HGRCPATH A list of files or directories to search for configuration files Item separator is on Unix on Windows If HGRCPATH is not set platform default search path is used If empty only the hg hgrc from the current repository is read For each element in HGRCPATH if it s a directory all files ending with rc are added otherwise the file itself will be added HGPLAIN When set this disables any configuration settings that might change Mercurial s default output This includes encoding defaults verbose mode debug mode quiet mode tracebacks and localization This can be useful when scripting against Mercurial in the face of existing user configuration Equivalent options set via command line flags or environment variables are not overridden HGPLAINEXCEPT This is a comma separated list of features to preserve when HGPLAIN is enabled Currently the only value supported is i18n which preserves internationalization in plain mode Setting HGPLAINEXCEPT to anything even an empty string will enable plain mode HGUSER This is the string used as the author of a commit If not set available values will be considered in this order HGUSER deprecated configuration files from the HGRCPATH EMAIL interactive prompt LOGNAME with

    Original URL path: http://vrasneur.coredump.fr/reporter/help/environment (2015-02-06)
    Open archived version from archive

  • reporter: Branches
    your configuration file like this extensions foo You may also specify the full path to an extension extensions myfeature hgext myfeature py To explicitly disable an extension enabled in a configuration file of broader scope prepend its path with extensions disabling extension bar residing in path to extension bar py bar path to extension bar py ditto but no path was supplied for extension baz baz disabled extensions acl hooks for controlling repository access bugzilla hooks for integrating with the Bugzilla bug tracker children command to display child changesets churn command to display statistics about repository history color colorize output from some commands convert import revisions from foreign VCS repositories into Mercurial eol automatically manage newlines in repository files extdiff command to allow external programs to compare revisions factotum http authentication with factotum fetch pull update and merge in one command gpg commands to sign and verify changesets graphlog command to view revision graphs from a shell hgcia hooks for integrating with the CIA vc notification service hgk browse the repository in a graphical way highlight syntax highlighting for hgweb requires Pygments inotify accelerate status report using Linux s inotify service interhg expand expressions into changelog and summaries keyword expand

    Original URL path: http://vrasneur.coredump.fr/reporter/help/extensions (2015-02-06)
    Open archived version from archive