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

v1.5.0 notes -- further rewording of old news items.

Junio C Hamano committed Dec 30, 2006 at 17:30 UTC d1c76fbe2671261cd2a200879b5aeff64cb61aa2
1 file changed +22 -21
v1.5.0.txt
+22 -21
@@ -7,36 +7,37 @@ Old news
7 This section is for people who are upgrading from ancient
8 versions of git. Although all of the changes in this section
9 happened before the current v1.4.4 release, they are summarized
10 -here in the v1.5.0 release notes for people who skip versions
11 -between upgrading.
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 -There is no need to perform "repository conversion". However,
15 -some of the changes are one-way street upgrades -- once you use
16 -the feature your repository cannot be used with ancient git.
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.
18
18 - - There is a new configuration variable core.legacyheaders that
19 + - There is a configuration variable core.legacyheaders that
20 changes the format of loose objects so that they are more
21 efficient to pack and to send out of the repository over git
21 - native protocol. However, this format cannot be read by git
22 - older than v1.4.2; people fetching from your repository using
23 - older clients over dumb transports (e.g. http) using older
24 - versions of git will also be affected. This is not enabled
25 - by default.
26 -
27 - - Another configuration repack.usedeltabaseoffset further
28 - allows packfile to be created in more space efficient format,
29 - which cannot be read by git older than v1.4.3. This is not
22 + native protocol, since v1.4.2. However, this format cannot
23 + be read by git older than that version; people fetching from
24 + your repository using older clients over dumb transports
25 + (e.g. http) using older versions of git will also be
26 + affected. This is not enabled by default.
27 +
28 + - Since v1.4.3, configuration repack.usedeltabaseoffset allows
29 + packfile to be created in more space efficient format, which
30 + cannot be read by git older than that version. This is not
31 enabled by default.
32
33 - 'git pack-refs' appeared in v1.4.4; this command allows tags
34 to be accessed much more efficiently than the traditional
35 'one-file-per-tag' format. Older git-native clients can
35 - fetch from a repository that packed its tags (the server side
36 - needs to run the up-to-date version of git), but older dumb
37 - transports cannot. Packing of refs is done by an explicit
38 - user action, either by use of "git pack-refs --prune" command
39 - or by use of "git gc" command.
36 + still fetch from a repository that packed and pruned refs
37 + (the server side needs to run the up-to-date version of git),
38 + but older dumb transports cannot. Packing of refs is done by
39 + an explicit user action, either by use of "git pack-refs
40 + --prune" command or by use of "git gc" command.
41
42 - 'git -p' to paginate anything -- many commands do pagination
43 by default on a tty. Introduced between v1.4.1 and v1.4.2;