@matheusbsbs / matheus-bagliano / commits / 449266469d
Fork 0

v1.5.0.txt : minor copyediting.

Junio C Hamano committed Jan 16, 2007 at 16:52 UTC 449266469dbf96be6e63fb6d7c8c0ac15e6bc79e
1 file changed +16 -14
v1.5.0.txt
+16 -14
@@ -168,9 +168,10 @@ Updates in v1.5.0 since v1.4.4 series
168
169 Existing repositories that have been using reflog may get
170 complaints from fsck-objects and may not be able to run
171 - git-repack; please run "git reflog expire --stale-fix --all"
172 - first to remove reflog entries that refer to commits that are
173 - no longer in the repository when that happens.
171 + git-repack, if you had run git-prune from older git; please
172 + run "git reflog expire --stale-fix --all" first to remove
173 + reflog entries that refer to commits that are no longer in
174 + the repository when that happens.
175
176 - git-branch knows how to rename branches and moves existing
177 reflog data from the old branch to the new one.
@@ -200,13 +201,14 @@ Updates in v1.5.0 since v1.4.4 series
201 checkout" refuses when the detached HEAD is not pointed by
202 any existing ref (an existing branch, a remote tracking
203 branch or a tag). This safety can be overriden with "git
203 - checout -f".
204 + checkout -f $branch".
205
206
207 * Packed refs
208
209 - Repositories with hundreds of tags have been paying large
209 - overhead, both in storage and in runtime. A new command,
210 + overhead, both in storage and in runtime, due to the
211 + traditional one-ref-per-file format. A new command,
212 git-pack-refs, can be used to "pack" them in more efficient
213 representation.
214
@@ -217,9 +219,9 @@ Updates in v1.5.0 since v1.4.4 series
219
220 * Configuration
221
220 - - configuration related to colorize setting are consolidated
221 - under color.* namespace (older diff.color.*, status.color.*
222 - are still supported).
222 + - configuration related to color setting are consolidated under
223 + color.* namespace (older diff.color.*, status.color.* are
224 + still supported).
225
226
227 * Less external dependency
@@ -260,10 +262,10 @@ Updates in v1.5.0 since v1.4.4 series
262 - Tools for e-mailed patch application now default to -u
263 behaviour; i.e. it always re-codes from the e-mailed encoding
264 to the encoding specified with i18n.commitencoding. This
263 - unfortunately forces projects that have happily using a
264 - legacy encoding without setting i18n.commitencoding, but
265 - taken with other improvement, please excuse us for this very
266 - minor one-time inconvenience.
265 + unfortunately forces projects that have happily been using a
266 + legacy encoding without setting i18n.commitencoding to set
267 + the configuration, but taken with other improvement, please
268 + excuse us for this very minor one-time inconvenience.
269
270
271 * Foreign SCM interfaces
@@ -297,8 +299,8 @@ Updates in v1.5.0 since v1.4.4 series
299 * Shallow clones
300
301 - There is a partial support for 'shallow' repositories that
300 - keeps only recent history now. A 'shallow clone' is created
301 - by specifying how deep that truncated history should be.
302 + keeps only recent history. A 'shallow clone' is created by
303 + specifying how deep that truncated history should be.
304
305 Currently a shallow repository has number of limitations:
306