author | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 17 Jan 2007 05:33:18 +0000 (00:33 -0500) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 17 Jan 2007 05:33:18 +0000 (00:33 -0500) | ||
commit | 2104838bf9b97066f21e4c32efdfa424d41e6b98 | |
tree | 76a4731ab02426ba2ead24bd6a76f7bcbf41dfe1 | tree | snapshot |
parent | 2369ed79071edf0f040eb2c280e1e2cf9a883bb9 | commit | diff |
Corrected BNF input documentation for fast-import.
Now that fast-import uses uintmax_t (the largest available unsigned
integer type) for marks we don't want to say its an unsigned 32
bit integer in ASCII base 10 notation. It could be much larger,
especially on 64 bit systems, and especially if a frontend uses
a very large number of marks (1 per file revision on a very, very
large import).
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Now that fast-import uses uintmax_t (the largest available unsigned
integer type) for marks we don't want to say its an unsigned 32
bit integer in ASCII base 10 notation. It could be much larger,
especially on 64 bit systems, and especially if a frontend uses
a very large number of marks (1 per file revision on a very, very
large import).
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
fast-import.c | diff | blob | history |