@matheusbsbs / matheus-bagliano / commits / f842fdb01d
Fork 0

Correct some language in fast-import documentation.

Minor documentation improvements, as suggested on the Git mailing list by Horst H. von Brand and Karl Hasselström. Signed-off-by: Shawn O. Pearce <spearce@spearce.org>

Shawn O. Pearce committed Feb 8, 2007 at 01:53 UTC f842fdb01da6037a8be4cf7f084bc6030f1eea5f
1 file changed +6 -5
Documentation/git-fast-import.txt
+6 -5
@@ -181,7 +181,7 @@ If the local offset is not available in the source material, use
181 ``+0000'', or the most common local offset. For example many
182 organizations have a CVS repository which has only ever been accessed
183 by users who are located in the same location and timezone. In this
184 -case the offset from UTC can be easily assumed.
184 +case a reasonable offset from UTC could be assumed.
185 +
186 Unlike the `rfc2822` format, this format is very strict. Any
187 variation in formatting will cause gfi to reject the value.
@@ -190,7 +190,7 @@ variation in formatting will cause gfi to reject the value.
190 This is the standard email format as described by RFC 2822.
191 +
192 An example value is ``Tue Feb 6 11:22:18 2007 -0500''. The Git
193 -parser is accurate, but a little on the lenient side. Its the
193 +parser is accurate, but a little on the lenient side. It is the
194 same parser used by gitlink:git-am[1] when applying patches
195 received from email.
196 +
@@ -205,14 +205,15 @@ contained in an RFC 2822 date string is used to adjust the date
205 value to UTC prior to storage. Therefore it is important that
206 this information be as accurate as possible.
207 +
208 -If the source material is formatted in RFC 2822 style dates,
208 +If the source material uses RFC 2822 style dates,
209 the frontend should let gfi handle the parsing and conversion
210 (rather than attempting to do it itself) as the Git parser has
211 been well tested in the wild.
212 +
213 Frontends should prefer the `raw` format if the source material
214 -is already in UNIX-epoch format, or is easily convertible to
215 -that format, as there is no ambiguity in parsing.
214 +already uses UNIX-epoch format, can be coaxed to give dates in that
215 +format, or its format is easiliy convertible to it, as there is no
216 +ambiguity in parsing.
217
218 `now`::
219 Always use the current time and timezone. The literal