v1.5.0.txt update (suggestions from Carl Worth)
Junio C Hamano committed
Jan 22, 2007 at 11:25 UTC
dba1f6e53c819bb8aaf8e96f7e592c2f228f45cd
1 file changed
+18
-12
v1.5.0.txt
+18
-12
@@ -10,11 +10,11 @@ happened before the current v1.4.4 release, they are summarized
10
here in the v1.5.0 release notes for people who skipped earlier
11
versions.
12
13
-In general, you should not have to worry about incompatibility,
14
-and there is no need to perform "repository conversion" if you
15
-are updating to v1.5.0. However, some of the changes are
16
-one-way street upgrades; once you use them your repository
17
-can no longer be used with ancient git.
13
+As of git v1.5.0 there are some optional features that changes
14
+the repository to allow data to be stored and transferred more
15
+efficiently. These features are not enabled by default, as they
16
+will make the repository unusable with older versions of git.
17
+Specifically, the available options are:
18
19
- There is a configuration variable core.legacyheaders that
20
changes the format of loose objects so that they are more
@@ -93,7 +93,9 @@ Updates in v1.5.0 since v1.4.4 series
93
- git-reset <tree> <paths>... can be used to revert index
94
entries for selected paths.
95
96
- - git-update-index is much less visible.
96
+ - git-update-index is much less visible. Many suggestions to
97
+ use the command in git output and documentation have now been
98
+ replaced by simpler commands such as "git add" or "git rm".
99
100
101
* Repository layout and objects transfer
@@ -200,14 +202,17 @@ Updates in v1.5.0 since v1.4.4 series
202
203
- There is a toplevel garbage collector script, 'git-gc', that
204
runs periodic cleanup functions, including 'git-repack -a -d',
203
- 'git-reflog expire', 'git-pack-refs --prune', and 'git-rerere gc'.
205
+ 'git-reflog expire', 'git-pack-refs --prune', and 'git-rerere
206
+ gc'.
207
208
209
* Detached HEAD
210
208
- - You can give non-branch to "git checkout" now. This will
209
- dissociate your HEAD from any of your branches. A typical
210
- use of this feature is to "look around". E.g.
211
+ - You can use 'git-checkout' to check out an arbitrary revision
212
+ or a tag as well, instead of named branches. This will
213
+ dissociate your HEAD from the branch you are currently on.
214
+
215
+ A typical use of this feature is to "look around". E.g.
216
217
$ git checkout v2.6.16
218
... compile, test, etc.
@@ -238,7 +243,7 @@ Updates in v1.5.0 since v1.4.4 series
243
overhead, both in storage and in runtime, due to the
244
traditional one-ref-per-file format. A new command,
245
git-pack-refs, can be used to "pack" them in more efficient
241
- representation.
246
+ representation (you can let git-gc do this for you).
247
248
- Clones and fetches over dumb transports are now aware of
249
packed refs and can download from repositories that use
@@ -343,7 +348,8 @@ Updates in v1.5.0 since v1.4.4 series
348
349
- There is a partial support for 'shallow' repositories that
350
keeps only recent history. A 'shallow clone' is created by
346
- specifying how deep that truncated history should be.
351
+ specifying how deep that truncated history should be
352
+ (e.g. "git clone --depth=5 git://some.where/repo.git").
353
354
Currently a shallow repository has number of limitations:
355