Martin Geisler <mg@lazybytes.net> [Thu, 22 Oct 2009 00:30:24 +0200] rev 9628
rst2man: highlight inline literals in bold
The old code would switch to Courier, but that doesn't really help
much in a manpage.
Martin Geisler <mg@lazybytes.net> [Thu, 22 Oct 2009 00:27:08 +0200] rev 9627
rst2man: avoid italic for references
The links to other manpages used both italic and bold text nested
within each other. The \fP (select previous font) macro was used
incorrectly to "reset" the nested fonts resulting in:
<roman> text <italic> <bold> hg <italic> (1) <bold> more text
with no switch back to roman. This stops the bleeding and removes the
ugly italic (underline) from the manpage links.
Martin Geisler <mg@lazybytes.net> [Wed, 21 Oct 2009 23:40:01 +0200] rev 9626
doc: add a style sheet to the generated HTML pages
Matt Mackall <mpm@selenic.com> [Wed, 21 Oct 2009 17:42:22 -0500] rev 9625
summary: remove reference to -p
Martin Geisler <mg@lazybytes.net> [Tue, 20 Oct 2009 22:43:17 +0200] rev 9624
doc, help: stream-line use of inline-literals
Martin Geisler <mg@lazybytes.net> [Tue, 20 Oct 2009 22:16:27 +0200] rev 9623
minirst: convert ``foo`` into "foo" upon display
This lets us markup many more occurances of inline literals since they
no longer look strange in the terminal output.
Martin Geisler <mg@lazybytes.net> [Tue, 20 Oct 2009 22:42:49 +0200] rev 9622
gendoc: fix synopsis
The synopsis is used as an inline literal when generating the manpage.
There should not be any whitespace on the inside of the quotation
marks in inline literals.
Commands with an empty synopsis (such as tags) produces ``tags `` as
synopsis, which triggers a warning.
Martin Geisler <mg@lazybytes.net> [Tue, 20 Oct 2009 22:39:37 +0200] rev 9621
test-debugcomplete: update output to match
a7ef354da662
Matt Mackall <mpm@selenic.com> [Tue, 20 Oct 2009 11:59:38 -0500] rev 9620
summary: add --remote
Matt Mackall <mpm@selenic.com> [Tue, 20 Oct 2009 11:58:09 -0500] rev 9619
summary: restore briefer commit status
Matt Mackall <mpm@selenic.com> [Tue, 20 Oct 2009 11:57:25 -0500] rev 9618
summary: add empty repository and no revision checked out hints
Matt Mackall <mpm@selenic.com> [Mon, 19 Oct 2009 23:53:25 -0500] rev 9617
Merge with crew
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Tue, 20 Oct 2009 00:30:36 +0200] rev 9616
merge with crew
Gilles Moris <gilles.moris@free.fr> [Sun, 18 Oct 2009 14:35:36 +0200] rev 9615
setup: refactor the version string to a subset of tag+tagdist-hash+date
Here is an array summarizing the mercurial version string:
[A] [B] [C] [D]
[1] clone tag clean => tag
[2] clone hash clean => latesttag+latesttagdistance-hash
[3] clone tag dirty => tag+date
[4] clone hash dirty => latesttag+latesttagdistance-hash+date
[5] archive tag clean => tag
[6] archive hash clean => latesttag+latesttagdistance-hash
Column [A]: Mercurial built from an hg *archive* or hg *clone* working directory
Column [B]: revision built has a *tag* or else default to the SHA1 *hash*
Column [C]: working tree *clean* or *dirty*
Column [D]: Mercurial version string
Over the previous version:
- row [5] did return just the node hash, now it returns the tag
- prepend the latest tag and the distance to it to rows [2][4][6]
- append also the date to row [3]; previously, it was just the tag
- the version string is with an empty string to avoid possible TypeError
exceptions during string manipulations
- factorize the function to run hg commands; remove the error message as it is
no more specific to the function.
This scheme enables to have first part of the version strings that can be
compared, whether it has been built from a tagged or untagged revision.
The second part of the version adds a hash for untagged revisions and today's
date if the working tree has local modifications.
As the version string does not contain spaces or special characters, it should
not break script parsing the 'hg version' command and should be usable for use
in file names.
The new code also ensure that the version string has exactly the same version
string, whether it has been built from an archive or from a clone.
Gilles Moris <gilles.moris@free.fr> [Tue, 11 Aug 2009 09:04:02 +0200] rev 9614
archive: add branch and tag informations to the .hg_archival.txt file
Up to this changeset, only the repo (first node) and current node hash were
included. This adds also the named branch and tags.
So the additional lines to .hg_archival.txt are
branch: the named branch
tag: the global tags of this revision, one per line in case of multiple tags
latesttag: if the revision is untagged, the latest tag (most recent in
ancestors), again one per line if this ancestor has multiple tags.
latestagdistance: the longest distance (changesets) to this latest ancestor.
Martin Geisler <mg@lazybytes.net> [Tue, 20 Oct 2009 00:17:36 +0200] rev 9613
ui: only use "user@host" as username in noninteractive mode
We regularly see people on IRC ask how they can correct commits they
accidentally made without having configured a username. This change
will make Mercurial abort when a commit is made without a username.
If Mercurial is run without a TTY (from a cronjob or similar), a
username is constructed as usual. Schematically the changes are as
follows:
With ui.askusername=False:
old new
interactive user@host abort
noninteractive user@host user@host
With ui.askusername=True:
old new
interactive prompt prompt
noninteractive user@host user@host