Mercurial > hg
view mercurial/help/dates.txt @ 13038:670f4e98276d stable
checknlink: return False if .hgtmp file preexists (issue2517)
If os_link fails on Windows, errno is always errno.EINVAL,
so we can't really say if the testlink could not be created
because (a) the FS doesn't support hardlinks or (b) there
is a leaked .hgtmp file lying around from a previous crashed
run.
So let's err on the safe side, keep the code simple and assume
we can't detect hardlinks in both cases.
author | Adrian Buehlmann <adrian@cadifra.com> |
---|---|
date | Tue, 23 Nov 2010 22:53:47 +0100 |
parents | f91e5630ce7e |
children | 0a0988bd4818 fe48c57390f2 |
line wrap: on
line source
Some commands allow the user to specify a date, e.g.: - backout, commit, import, tag: Specify the commit date. - log, revert, update: Select revision(s) by date. Many date formats are valid. Here are some examples: - ``Wed Dec 6 13:18:29 2006`` (local timezone assumed) - ``Dec 6 13:18 -0600`` (year assumed, time offset provided) - ``Dec 6 13:18 UTC`` (UTC and GMT are aliases 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. unixtime is the number of seconds since the epoch (1970-01-01 00:00 UTC). offset is the offset of the local timezone, in seconds west of UTC (negative if the timezone is east of UTC). The log command also accepts date ranges: - ``<{datetime}`` - at or before a given date/time - ``>{datetime}`` - on or after a given date/time - ``{datetime} to {datetime}`` - a date range, inclusive - ``-{days}`` - within a given number of days of today