FM / RelNotes

/usr/share/doc/git/RelNotes

Name	Size	Mode	Actions
1.5.0.1.txt	1255	0644	edit dl rm
1.5.0.2.txt	2308	0644	edit dl rm
1.5.0.3.txt	1577	0644	edit dl rm
1.5.0.4.txt	462	0644	edit dl rm
1.5.0.5.txt	609	0644	edit dl rm
1.5.0.6.txt	484	0644	edit dl rm
1.5.0.7.txt	482	0644	edit dl rm
1.5.0.txt	18638	0644	edit dl rm
1.5.1.1.txt	2164	0644	edit dl rm
1.5.1.2.txt	1651	0644	edit dl rm
1.5.1.3.txt	1566	0644	edit dl rm
1.5.1.4.txt	843	0644	edit dl rm
1.5.1.5.txt	1430	0644	edit dl rm
1.5.1.6.txt	1519	0644	edit dl rm
1.5.1.txt	13288	0644	edit dl rm
1.5.2.1.txt	1457	0644	edit dl rm
1.5.2.2.txt	2086	0644	edit dl rm
1.5.2.3.txt	796	0644	edit dl rm
1.5.2.4.txt	802	0644	edit dl rm
1.5.2.5.txt	928	0644	edit dl rm
1.5.2.txt	7355	0644	edit dl rm
1.5.3.1.txt	326	0644	edit dl rm
1.5.3.2.txt	1931	0644	edit dl rm
1.5.3.3.txt	896	0644	edit dl rm
1.5.3.4.txt	1208	0644	edit dl rm
1.5.3.5.txt	3376	0644	edit dl rm
1.5.3.6.txt	1432	0644	edit dl rm
1.5.3.7.txt	1584	0644	edit dl rm
1.5.3.8.txt	783	0644	edit dl rm
1.5.3.txt	14030	0644	edit dl rm
1.5.4.1.txt	524	0644	edit dl rm
1.5.4.2.txt	1530	0644	edit dl rm
1.5.4.3.txt	997	0644	edit dl rm
1.5.4.4.txt	2617	0644	edit dl rm
1.5.4.5.txt	2241	0644	edit dl rm
1.5.4.6.txt	1440	0644	edit dl rm
1.5.4.7.txt	342	0644	edit dl rm
1.5.4.txt	14424	0644	edit dl rm
1.5.5.1.txt	1499	0644	edit dl rm
1.5.5.2.txt	772	0644	edit dl rm
1.5.5.3.txt	305	0644	edit dl rm
1.5.5.4.txt	140	0644	edit dl rm
1.5.5.5.txt	449	0644	edit dl rm
1.5.5.6.txt	342	0644	edit dl rm
1.5.5.txt	7596	0644	edit dl rm
1.5.6.1.txt	793	0644	edit dl rm
1.5.6.2.txt	1457	0644	edit dl rm
1.5.6.3.txt	2113	0644	edit dl rm
1.5.6.4.txt	1573	0644	edit dl rm
1.5.6.5.txt	1041	0644	edit dl rm
1.5.6.6.txt	342	0644	edit dl rm
1.5.6.txt	3843	0644	edit dl rm
1.6.0.1.txt	1188	0644	edit dl rm
1.6.0.2.txt	2840	0644	edit dl rm
1.6.0.3.txt	4315	0644	edit dl rm
1.6.0.4.txt	1293	0644	edit dl rm
1.6.0.5.txt	2014	0644	edit dl rm
1.6.0.6.txt	1193	0644	edit dl rm
1.6.0.txt	10049	0644	edit dl rm
1.6.1.1.txt	1976	0644	edit dl rm
1.6.1.2.txt	1640	0644	edit dl rm
1.6.1.3.txt	847	0644	edit dl rm
1.6.1.4.txt	1593	0644	edit dl rm
1.6.1.txt	10322	0644	edit dl rm
1.6.2.1.txt	597	0644	edit dl rm
1.6.2.2.txt	1508	0644	edit dl rm
1.6.2.3.txt	781	0644	edit dl rm
1.6.2.4.txt	1351	0644	edit dl rm
1.6.2.5.txt	688	0644	edit dl rm
1.6.2.txt	5888	0644	edit dl rm
1.6.3.1.txt	343	0644	edit dl rm
1.6.3.2.txt	2271	0644	edit dl rm
1.6.3.3.txt	1379	0644	edit dl rm
1.6.3.4.txt	1206	0644	edit dl rm
1.6.3.txt	6787	0644	edit dl rm
1.6.4.1.txt	1906	0644	edit dl rm
1.6.4.2.txt	1210	0644	edit dl rm
1.6.4.3.txt	1146	0644	edit dl rm
1.6.4.4.txt	1034	0644	edit dl rm
1.6.4.5.txt	605	0644	edit dl rm
1.6.4.txt	5353	0644	edit dl rm
1.6.5.1.txt	549	0644	edit dl rm
1.6.5.2.txt	581	0644	edit dl rm
1.6.5.3.txt	2485	0644	edit dl rm
1.6.5.4.txt	1274	0644	edit dl rm
1.6.5.5.txt	1891	0644	edit dl rm
1.6.5.6.txt	791	0644	edit dl rm
1.6.5.7.txt	771	0644	edit dl rm
1.6.5.8.txt	900	0644	edit dl rm
1.6.5.9.txt	581	0644	edit dl rm
1.6.5.txt	6290	0644	edit dl rm
1.6.6.1.txt	1230	0644	edit dl rm
1.6.6.2.txt	1599	0644	edit dl rm
1.6.6.3.txt	751	0644	edit dl rm
1.6.6.txt	9459	0644	edit dl rm
1.7.0.1.txt	1287	0644	edit dl rm
1.7.0.2.txt	1476	0644	edit dl rm
1.7.0.3.txt	1176	0644	edit dl rm
1.7.0.4.txt	888	0644	edit dl rm
1.7.0.5.txt	915	0644	edit dl rm
1.7.0.6.txt	365	0644	edit dl rm
1.7.0.7.txt	467	0644	edit dl rm
1.7.0.8.txt	452	0644	edit dl rm
1.7.0.9.txt	219	0644	edit dl rm
1.7.0.txt	8765	0644	edit dl rm
1.7.1.1.txt	3825	0644	edit dl rm
1.7.1.2.txt	1069	0644	edit dl rm
1.7.1.3.txt	452	0644	edit dl rm
1.7.1.4.txt	219	0644	edit dl rm
1.7.1.txt	2941	0644	edit dl rm
1.7.2.1.txt	806	0644	edit dl rm
1.7.2.2.txt	695	0644	edit dl rm
1.7.2.3.txt	1355	0644	edit dl rm
1.7.2.4.txt	452	0644	edit dl rm
1.7.2.5.txt	219	0644	edit dl rm
1.7.2.txt	5978	0644	edit dl rm
1.7.3.1.txt	425	0644	edit dl rm
1.7.3.2.txt	149	0644	edit dl rm
1.7.3.3.txt	2075	0644	edit dl rm
1.7.3.4.txt	1639	0644	edit dl rm
1.7.3.5.txt	1454	0644	edit dl rm
1.7.3.txt	2642	0644	edit dl rm
1.7.4.1.txt	899	0644	edit dl rm
1.7.4.2.txt	2290	0644	edit dl rm
1.7.4.3.txt	1245	0644	edit dl rm
1.7.4.4.txt	1288	0644	edit dl rm
1.7.4.5.txt	127	0644	edit dl rm
1.7.4.txt	6502	0644	edit dl rm
1.7.5.1.txt	1905	0644	edit dl rm
1.7.5.2.txt	2189	0644	edit dl rm
1.7.5.3.txt	1101	0644	edit dl rm
1.7.5.4.txt	754	0644	edit dl rm
1.7.5.txt	5329	0644	edit dl rm
1.7.6.1.txt	2248	0644	edit dl rm
1.7.6.2.txt	245	0644	edit dl rm
1.7.6.3.txt	792	0644	edit dl rm
1.7.6.4.txt	1264	0644	edit dl rm
1.7.6.5.txt	969	0644	edit dl rm
1.7.6.6.txt	587	0644	edit dl rm
1.7.6.txt	5507	0644	edit dl rm
1.7.7.1.txt	2432	0644	edit dl rm
1.7.7.2.txt	1630	0644	edit dl rm
1.7.7.3.txt	696	0644	edit dl rm
1.7.7.4.txt	444	0644	edit dl rm
1.7.7.5.txt	481	0644	edit dl rm
1.7.7.6.txt	791	0644	edit dl rm
1.7.7.7.txt	334	0644	edit dl rm
1.7.7.txt	5408	0644	edit dl rm
1.7.8.1.txt	1438	0644	edit dl rm
1.7.8.2.txt	2925	0644	edit dl rm
1.7.8.3.txt	431	0644	edit dl rm
1.7.8.4.txt	921	0644	edit dl rm
1.7.8.5.txt	606	0644	edit dl rm
1.7.8.6.txt	621	0644	edit dl rm
1.7.8.txt	6351	0644	edit dl rm
1.7.9.1.txt	2461	0644	edit dl rm
1.7.9.2.txt	2706	0644	edit dl rm
1.7.9.3.txt	1958	0644	edit dl rm
1.7.9.4.txt	887	0644	edit dl rm
1.7.9.5.txt	731	0644	edit dl rm
1.7.9.6.txt	432	0644	edit dl rm
1.7.9.7.txt	371	0644	edit dl rm
1.7.9.txt	4373	0644	edit dl rm
1.7.10.1.txt	3073	0644	edit dl rm
1.7.10.2.txt	3445	0644	edit dl rm
1.7.10.3.txt	1876	0644	edit dl rm
1.7.10.4.txt	1057	0644	edit dl rm
1.7.10.5.txt	397	0644	edit dl rm
1.7.10.txt	9025	0644	edit dl rm
1.7.11.1.txt	224	0644	edit dl rm
1.7.11.2.txt	2291	0644	edit dl rm
1.7.11.3.txt	2314	0644	edit dl rm
1.7.11.4.txt	1171	0644	edit dl rm
1.7.11.5.txt	1292	0644	edit dl rm
1.7.11.6.txt	3436	0644	edit dl rm
1.7.11.7.txt	1959	0644	edit dl rm
1.7.11.txt	5506	0644	edit dl rm
1.7.12.1.txt	5800	0644	edit dl rm
1.7.12.2.txt	1767	0644	edit dl rm
1.7.12.3.txt	1329	0644	edit dl rm
1.7.12.4.txt	712	0644	edit dl rm
1.7.12.txt	5336	0644	edit dl rm
1.8.0.1.txt	2454	0644	edit dl rm
1.8.0.2.txt	1250	0644	edit dl rm
1.8.0.3.txt	424	0644	edit dl rm
1.8.0.txt	11072	0644	edit dl rm
1.8.1.1.txt	3577	0644	edit dl rm
1.8.1.2.txt	991	0644	edit dl rm
1.8.1.3.txt	1740	0644	edit dl rm
1.8.1.4.txt	337	0644	edit dl rm
1.8.1.5.txt	1940	0644	edit dl rm
1.8.1.6.txt	1563	0644	edit dl rm
1.8.1.txt	9624	0644	edit dl rm
1.8.2.1.txt	4561	0644	edit dl rm
1.8.2.2.txt	2438	0644	edit dl rm
1.8.2.3.txt	672	0644	edit dl rm
1.8.2.txt	22140	0644	edit dl rm
1.8.3.1.txt	433	0644	edit dl rm
1.8.3.2.txt	2406	0644	edit dl rm
1.8.3.3.txt	1778	0644	edit dl rm
1.8.3.4.txt	700	0644	edit dl rm
1.8.3.txt	18336	0644	edit dl rm
1.8.4.1.txt	3012	0644	edit dl rm
1.8.4.2.txt	3294	0644	edit dl rm
1.8.4.3.txt	2208	0644	edit dl rm
1.8.4.4.txt	342	0644	edit dl rm
1.8.4.5.txt	421	0644	edit dl rm
1.8.4.txt	21258	0644	edit dl rm
1.8.5.1.txt	254	0644	edit dl rm
1.8.5.2.txt	656	0644	edit dl rm
1.8.5.3.txt	859	0644	edit dl rm
1.8.5.4.txt	1912	0644	edit dl rm
1.8.5.5.txt	1466	0644	edit dl rm
1.8.5.6.txt	1686	0644	edit dl rm
1.8.5.txt	20348	0644	edit dl rm
1.9.0.txt	15197	0644	edit dl rm
1.9.1.txt	2409	0644	edit dl rm
1.9.2.txt	2807	0644	edit dl rm
1.9.3.txt	635	0644	edit dl rm
1.9.4.txt	607	0644	edit dl rm
1.9.5.txt	1678	0644	edit dl rm
2.0.0.txt	15911	0644	edit dl rm
2.0.1.txt	5171	0644	edit dl rm
2.0.2.txt	1350	0644	edit dl rm
2.0.3.txt	592	0644	edit dl rm
2.0.4.txt	153	0644	edit dl rm
2.0.5.txt	1678	0644	edit dl rm
2.1.0.txt	17336	0644	edit dl rm
2.1.1.txt	1806	0644	edit dl rm
2.1.2.txt	768	0644	edit dl rm
2.1.3.txt	970	0644	edit dl rm
2.1.4.txt	1678	0644	edit dl rm
2.2.0.txt	13338	0644	edit dl rm
2.2.1.txt	1674	0644	edit dl rm
2.2.2.txt	2357	0644	edit dl rm
2.2.3.txt	284	0644	edit dl rm
2.3.0.txt	12859	0644	edit dl rm
2.3.1.txt	1998	0644	edit dl rm
2.3.2.txt	3009	0644	edit dl rm
2.3.3.txt	1523	0644	edit dl rm
2.3.4.txt	1150	0644	edit dl rm
2.3.5.txt	1767	0644	edit dl rm
2.3.6.txt	400	0644	edit dl rm
2.3.7.txt	762	0644	edit dl rm
2.3.8.txt	814	0644	edit dl rm
2.3.9.txt	284	0644	edit dl rm
2.3.10.txt	711	0644	edit dl rm
2.4.0.txt	22110	0644	edit dl rm
2.4.1.txt	1654	0644	edit dl rm
2.4.2.txt	1954	0644	edit dl rm
2.4.3.txt	3066	0644	edit dl rm
2.4.4.txt	1230	0644	edit dl rm
2.4.5.txt	1066	0644	edit dl rm
2.4.6.txt	744	0644	edit dl rm
2.4.7.txt	2213	0644	edit dl rm
2.4.8.txt	704	0644	edit dl rm
2.4.9.txt	284	0644	edit dl rm
2.4.10.txt	711	0644	edit dl rm
2.4.11.txt	424	0644	edit dl rm
2.4.12.txt	479	0644	edit dl rm
2.5.0.txt	26158	0644	edit dl rm
2.5.1.txt	2861	0644	edit dl rm
2.5.2.txt	2654	0644	edit dl rm
2.5.3.txt	565	0644	edit dl rm
2.5.4.txt	709	0644	edit dl rm
2.5.5.txt	420	0644	edit dl rm
2.5.6.txt	475	0644	edit dl rm
2.6.0.txt	16434	0644	edit dl rm
2.6.1.txt	705	0644	edit dl rm
2.6.2.txt	2678	0644	edit dl rm
2.6.3.txt	4904	0644	edit dl rm
2.6.4.txt	2163	0644	edit dl rm
2.6.5.txt	2542	0644	edit dl rm
2.6.6.txt	420	0644	edit dl rm
2.6.7.txt	475	0644	edit dl rm
2.7.0.txt	17498	0644	edit dl rm
2.7.1.txt	3533	0644	edit dl rm
2.7.2.txt	1739	0644	edit dl rm
2.7.3.txt	2597	0644	edit dl rm
2.7.4.txt	420	0644	edit dl rm
2.7.5.txt	544	0644	edit dl rm
2.7.6.txt	951	0644	edit dl rm
2.8.0.txt	19677	0644	edit dl rm
2.8.1.txt	255	0644	edit dl rm
2.8.2.txt	2704	0644	edit dl rm
2.8.3.txt	4433	0644	edit dl rm
2.8.4.txt	3061	0644	edit dl rm
2.8.5.txt	475	0644	edit dl rm
2.8.6.txt	122	0644	edit dl rm
2.9.0.txt	21836	0644	edit dl rm
2.9.1.txt	4930	0644	edit dl rm
2.9.2.txt	427	0644	edit dl rm
2.9.3.txt	7466	0644	edit dl rm
2.9.4.txt	4384	0644	edit dl rm
2.9.5.txt	122	0644	edit dl rm
2.10.0.txt	30132	0644	edit dl rm
2.10.1.txt	5730	0644	edit dl rm
2.10.2.txt	5298	0644	edit dl rm
2.10.3.txt	2353	0644	edit dl rm
2.10.4.txt	124	0644	edit dl rm
2.10.5.txt	561	0644	edit dl rm
2.11.0.txt	27992	0644	edit dl rm
2.11.1.txt	6815	0644	edit dl rm
2.11.2.txt	479	0644	edit dl rm
2.11.3.txt	124	0644	edit dl rm
2.11.4.txt	561	0644	edit dl rm
2.12.0.txt	22093	0644	edit dl rm
2.12.1.txt	1611	0644	edit dl rm
2.12.2.txt	3614	0644	edit dl rm
2.12.3.txt	2539	0644	edit dl rm
2.12.4.txt	124	0644	edit dl rm
2.12.5.txt	561	0644	edit dl rm
2.13.0.txt	28222	0644	edit dl rm
2.13.1.txt	5026	0644	edit dl rm
2.13.2.txt	2178	0644	edit dl rm
2.13.3.txt	2388	0644	edit dl rm
2.13.4.txt	1078	0644	edit dl rm
2.13.5.txt	124	0644	edit dl rm
2.13.6.txt	561	0644	edit dl rm
2.13.7.txt	780	0644	edit dl rm
2.14.0.txt	22728	0644	edit dl rm
2.14.1.txt	124	0644	edit dl rm
2.14.2.txt	4486	0644	edit dl rm
2.14.3.txt	4010	0644	edit dl rm
2.14.4.txt	167	0644	edit dl rm
2.14.5.txt	578	0644	edit dl rm
2.14.6.txt	2144	0644	edit dl rm
2.15.0.txt	21971	0644	edit dl rm
2.15.1.txt	3434	0644	edit dl rm
2.15.2.txt	1894	0644	edit dl rm
2.15.3.txt	210	0644	edit dl rm
2.15.4.txt	482	0644	edit dl rm
2.16.0.txt	20744	0644	edit dl rm
2.16.1.txt	305	0644	edit dl rm
2.16.2.txt	1083	0644	edit dl rm
2.16.3.txt	1757	0644	edit dl rm
2.16.4.txt	167	0644	edit dl rm
2.16.5.txt	210	0644	edit dl rm
2.16.6.txt	333	0644	edit dl rm
2.17.0.txt	17884	0644	edit dl rm
2.17.1.txt	617	0644	edit dl rm
2.17.2.txt	493	0644	edit dl rm
2.17.3.txt	490	0644	edit dl rm
2.17.4.txt	520	0644	edit dl rm
2.17.5.txt	828	0644	edit dl rm
2.17.6.txt	511	0644	edit dl rm
2.18.0.txt	26784	0644	edit dl rm
2.18.1.txt	227	0644	edit dl rm
2.18.2.txt	343	0644	edit dl rm
2.18.3.txt	167	0644	edit dl rm
2.18.4.txt	167	0644	edit dl rm
2.18.5.txt	207	0644	edit dl rm
2.19.0.txt	28138	0644	edit dl rm
2.19.1.txt	227	0644	edit dl rm
2.19.2.txt	4446	0644	edit dl rm
2.19.3.txt	343	0644	edit dl rm
2.19.4.txt	167	0644	edit dl rm
2.19.5.txt	167	0644	edit dl rm
2.19.6.txt	221	0644	edit dl rm
2.20.0.txt	32536	0644	edit dl rm
2.20.1.txt	616	0644	edit dl rm
2.20.2.txt	828	0644	edit dl rm
2.20.3.txt	167	0644	edit dl rm
2.20.4.txt	167	0644	edit dl rm
2.20.5.txt	230	0644	edit dl rm
2.21.0.txt	20130	0644	edit dl rm
2.21.1.txt	530	0644	edit dl rm
2.21.2.txt	167	0644	edit dl rm
2.21.3.txt	167	0644	edit dl rm
2.21.4.txt	239	0644	edit dl rm
2.22.0.txt	26979	0644	edit dl rm
2.22.1.txt	6233	0644	edit dl rm
2.22.2.txt	377	0644	edit dl rm
2.22.3.txt	167	0644	edit dl rm
2.22.4.txt	167	0644	edit dl rm
2.22.5.txt	248	0644	edit dl rm
2.23.0.txt	13943	0644	edit dl rm
2.23.1.txt	377	0644	edit dl rm
2.23.2.txt	167	0644	edit dl rm
2.23.3.txt	167	0644	edit dl rm
2.23.4.txt	257	0644	edit dl rm
2.24.0.txt	17750	0644	edit dl rm
2.24.1.txt	377	0644	edit dl rm
2.24.2.txt	167	0644	edit dl rm
2.24.3.txt	167	0644	edit dl rm
2.24.4.txt	266	0644	edit dl rm
2.25.0.txt	16410	0644	edit dl rm
2.25.1.txt	2141	0644	edit dl rm
2.25.2.txt	2494	0644	edit dl rm
2.25.3.txt	167	0644	edit dl rm
2.25.4.txt	167	0644	edit dl rm
2.25.5.txt	275	0644	edit dl rm
2.26.0.txt	14305	0644	edit dl rm
2.26.1.txt	167	0644	edit dl rm
2.26.2.txt	167	0644	edit dl rm
2.26.3.txt	284	0644	edit dl rm
2.27.0.txt	23519	0644	edit dl rm
2.27.1.txt	293	0644	edit dl rm
2.28.0.txt	9709	0644	edit dl rm
2.28.1.txt	302	0644	edit dl rm
2.29.0.txt	23314	0644	edit dl rm
2.29.1.txt	487	0644	edit dl rm
2.29.2.txt	331	0644	edit dl rm
2.29.3.txt	311	0644	edit dl rm
2.30.0.txt	17380	0644	edit dl rm
2.30.1.txt	1967	0644	edit dl rm
2.30.2.txt	320	0644	edit dl rm
2.31.0.txt	15390	0644	edit dl rm
2.31.1.txt	895	0644	edit dl rm
2.32.0.txt	17430	0644	edit dl rm
2.33.0.txt	12237	0644	edit dl rm
2.33.1.txt	5164	0644	edit dl rm
2.34.0.txt	18182	0644	edit dl rm
2.34.1.txt	794	0644	edit dl rm

Edit: /usr/share/doc/git/RelNotes/1.5.0.txt (18638B)

GIT v1.5.0 Release Notes
========================

Old news
--------

This section is for people who are upgrading from ancient
versions of git.  Although all of the changes in this section
happened before the current v1.4.4 release, they are summarized
here in the v1.5.0 release notes for people who skipped earlier
versions.

As of git v1.5.0 there are some optional features that changes
the repository to allow data to be stored and transferred more
efficiently.  These features are not enabled by default, as they
will make the repository unusable with older versions of git.
Specifically, the available options are:

- There is a configuration variable core.legacyheaders that
   changes the format of loose objects so that they are more
   efficient to pack and to send out of the repository over git
   native protocol, since v1.4.2.  However, loose objects
   written in the new format cannot be read by git older than
   that version; people fetching from your repository using
   older clients over dumb transports (e.g. http) using older
   versions of git will also be affected.

To let git use the new loose object format, you have to
   set core.legacyheaders to false.

- Since v1.4.3, configuration repack.usedeltabaseoffset allows
   packfile to be created in more space efficient format, which
   cannot be read by git older than that version.

To let git use the new format for packfiles, you have to
   set repack.usedeltabaseoffset to true.

The above two new features are not enabled by default and you
have to explicitly ask for them, because they make repositories
unreadable by older versions of git, and in v1.5.0 we still do
not enable them by default for the same reason.  We will change
this default probably 1 year after 1.4.2's release, when it is
reasonable to expect everybody to have new enough version of
git.

- 'git pack-refs' appeared in v1.4.4; this command allows tags
   to be accessed much more efficiently than the traditional
   'one-file-per-tag' format.  Older git-native clients can
   still fetch from a repository that packed and pruned refs
   (the server side needs to run the up-to-date version of git),
   but older dumb transports cannot.  Packing of refs is done by
   an explicit user action, either by use of "git pack-refs
   --prune" command or by use of "git gc" command.

- 'git -p' to paginate anything -- many commands do pagination
   by default on a tty.  Introduced between v1.4.1 and v1.4.2;
   this may surprise old timers.

- 'git archive' superseded 'git tar-tree' in v1.4.3;

- 'git cvsserver' was new invention in v1.3.0;

- 'git repo-config', 'git grep', 'git rebase' and 'gitk' were
   seriously enhanced during v1.4.0 timeperiod.

- 'gitweb' became part of git.git during v1.4.0 timeperiod and
   seriously modified since then.

- reflog is an v1.4.0 invention.  This allows you to name a
   revision that a branch used to be at (e.g. "git diff
   master@{yesterday} master" allows you to see changes since
   yesterday's tip of the branch).

Updates in v1.5.0 since v1.4.4 series
-------------------------------------

* Index manipulation

- git-add is to add contents to the index (aka "staging area"
   for the next commit), whether the file the contents happen to
   be is an existing one or a newly created one.

- git-add without any argument does not add everything
   anymore.  Use 'git-add .' instead.  Also you can add
   otherwise ignored files with an -f option.

- git-add tries to be more friendly to users by offering an
   interactive mode ("git-add -i").

- git-commit <path> used to refuse to commit if <path> was
   different between HEAD and the index (i.e. update-index was
   used on it earlier).  This check was removed.

- git-rm is much saner and safer.  It is used to remove paths
   from both the index file and the working tree, and makes sure
   you are not losing any local modification before doing so.

- git-reset <tree> <paths>... can be used to revert index
   entries for selected paths.

- git-update-index is much less visible.  Many suggestions to
   use the command in git output and documentation have now been
   replaced by simpler commands such as "git add" or "git rm".

* Repository layout and objects transfer

- The data for origin repository is stored in the configuration
   file $GIT_DIR/config, not in $GIT_DIR/remotes/, for newly
   created clones.  The latter is still supported and there is
   no need to convert your existing repository if you are
   already comfortable with your workflow with the layout.

- git-clone always uses what is known as "separate remote"
   layout for a newly created repository with a working tree.

A repository with the separate remote layout starts with only
   one default branch, 'master', to be used for your own
   development.  Unlike the traditional layout that copied all
   the upstream branches into your branch namespace (while
   renaming their 'master' to your 'origin'), the new layout
   puts upstream branches into local "remote-tracking branches"
   with their own namespace. These can be referenced with names
   such as "origin/$upstream_branch_name" and are stored in
   .git/refs/remotes rather than .git/refs/heads where normal
   branches are stored.

This layout keeps your own branch namespace less cluttered,
   avoids name collision with your upstream, makes it possible
   to automatically track new branches created at the remote
   after you clone from it, and makes it easier to interact with
   more than one remote repository (you can use "git remote" to
   add other repositories to track).  There might be some
   surprises:

* 'git branch' does not show the remote tracking branches.
     It only lists your own branches.  Use '-r' option to view
     the tracking branches.

* If you are forking off of a branch obtained from the
     upstream, you would have done something like 'git branch
     my-next next', because traditional layout dropped the
     tracking branch 'next' into your own branch namespace.
     With the separate remote layout, you say 'git branch next
     origin/next', which allows you to use the matching name
     'next' for your own branch.  It also allows you to track a
     remote other than 'origin' (i.e. where you initially cloned
     from) and fork off of a branch from there the same way
     (e.g. "git branch mingw j6t/master").

Repositories initialized with the traditional layout continue
   to work.

- New branches that appear on the origin side after a clone is
   made are also tracked automatically.  This is done with an
   wildcard refspec "refs/heads/*:refs/remotes/origin/*", which
   older git does not understand, so if you clone with 1.5.0,
   you would need to downgrade remote.*.fetch in the
   configuration file to specify each branch you are interested
   in individually if you plan to fetch into the repository with
   older versions of git (but why would you?).

- Similarly, wildcard refspec "refs/heads/*:refs/remotes/me/*"
   can be given to "git-push" command to update the tracking
   branches that is used to track the repository you are pushing
   from on the remote side.

- git-branch and git-show-branch know remote tracking branches
   (use the command line switch "-r" to list only tracked branches).

- git-push can now be used to delete a remote branch or a tag.
   This requires the updated git on the remote side (use "git
   push <remote> :refs/heads/<branch>" to delete "branch").

- git-push more aggressively keeps the transferred objects
   packed.  Earlier we recommended to monitor amount of loose
   objects and repack regularly, but you should repack when you
   accumulated too many small packs this way as well.  Updated
   git-count-objects helps you with this.

- git-fetch also more aggressively keeps the transferred objects
   packed.  This behavior of git-push and git-fetch can be
   tweaked with a single configuration transfer.unpacklimit (but
   usually there should not be any need for a user to tweak it).

- A new command, git-remote, can help you manage your remote
   tracking branch definitions.

- You may need to specify explicit paths for upload-pack and/or
   receive-pack due to your ssh daemon configuration on the
   other end.  This can now be done via remote.*.uploadpack and
   remote.*.receivepack configuration.

* Bare repositories

- Certain commands change their behavior in a bare repository
   (i.e. a repository without associated working tree).  We use
   a fairly conservative heuristic (if $GIT_DIR is ".git", or
   ends with "/.git", the repository is not bare) to decide if a
   repository is bare, but "core.bare" configuration variable
   can be used to override the heuristic when it misidentifies
   your repository.

- git-fetch used to complain updating the current branch but
   this is now allowed for a bare repository.  So is the use of
   'git-branch -f' to update the current branch.

- Porcelain-ish commands that require a working tree refuses to
   work in a bare repository.

* Reflog

- Reflog records the history from the view point of the local
   repository. In other words, regardless of the real history,
   the reflog shows the history as seen by one particular
   repository (this enables you to ask "what was the current
   revision in _this_ repository, yesterday at 1pm?").  This
   facility is enabled by default for repositories with working
   trees, and can be accessed with the "branch@{time}" and
   "branch@{Nth}" notation.

- "git show-branch" learned showing the reflog data with the
   new -g option.  "git log" has -g option to view reflog
   entries in a more verbose manner.

- git-branch knows how to rename branches and moves existing
   reflog data from the old branch to the new one.

- In addition to the reflog support in v1.4.4 series, HEAD
   reference maintains its own log.  "HEAD@{5.minutes.ago}"
   means the commit you were at 5 minutes ago, which takes
   branch switching into account.  If you want to know where the
   tip of your current branch was at 5 minutes ago, you need to
   explicitly say its name (e.g. "master@{5.minutes.ago}") or
   omit the refname altogether i.e. "@{5.minutes.ago}".

- The commits referred to by reflog entries are now protected
   against pruning.  The new command "git reflog expire" can be
   used to truncate older reflog entries and entries that refer
   to commits that have been pruned away previously with older
   versions of git.

Existing repositories that have been using reflog may get
   complaints from fsck-objects and may not be able to run
   git-repack, if you had run git-prune from older git; please
   run "git reflog expire --stale-fix --all" first to remove
   reflog entries that refer to commits that are no longer in
   the repository when that happens.

* Cruft removal

- We used to say "old commits are retrievable using reflog and
   'master@{yesterday}' syntax as long as you haven't run
   git-prune".  We no longer have to say the latter half of the
   above sentence, as git-prune does not remove things reachable
   from reflog entries.

- There is a toplevel garbage collector script, 'git-gc', that
   runs periodic cleanup functions, including 'git-repack -a -d',
   'git-reflog expire', 'git-pack-refs --prune', and 'git-rerere
   gc'.

- The output from fsck ("fsck-objects" is called just "fsck"
   now, but the old name continues to work) was needlessly
   alarming in that it warned missing objects that are reachable
   only from dangling objects.  This has been corrected and the
   output is much more useful.

* Detached HEAD

- You can use 'git-checkout' to check out an arbitrary revision
   or a tag as well, instead of named branches.  This will
   dissociate your HEAD from the branch you are currently on.

A typical use of this feature is to "look around".  E.g.

$ git checkout v2.6.16
	... compile, test, etc.
	$ git checkout v2.6.17
	... compile, test, etc.

- After detaching your HEAD, you can go back to an existing
   branch with usual "git checkout $branch".  Also you can
   start a new branch using "git checkout -b $newbranch" to
   start a new branch at that commit.

- You can even pull from other repositories, make merges and
   commits while your HEAD is detached.  Also you can use "git
   reset" to jump to arbitrary commit, while still keeping your
   HEAD detached.

Remember that a detached state is volatile, i.e. it will be forgotten
   as soon as you move away from it with the checkout or reset command,
   unless a branch is created from it as mentioned above.  It is also
   possible to rescue a lost detached state from the HEAD reflog.

* Packed refs

- Repositories with hundreds of tags have been paying large
   overhead, both in storage and in runtime, due to the
   traditional one-ref-per-file format.  A new command,
   git-pack-refs, can be used to "pack" them in more efficient
   representation (you can let git-gc do this for you).

- Clones and fetches over dumb transports are now aware of
   packed refs and can download from repositories that use
   them.

* Configuration

- configuration related to color setting are consolidated under
   color.* namespace (older diff.color.*, status.color.* are
   still supported).

- 'git-repo-config' command is accessible as 'git-config' now.

* Updated features

- git-describe uses better criteria to pick a base ref.  It
   used to pick the one with the newest timestamp, but now it
   picks the one that is topologically the closest (that is,
   among ancestors of commit C, the ref T that has the shortest
   output from "git-rev-list T..C" is chosen).

- git-describe gives the number of commits since the base ref
   between the refname and the hash suffix.  E.g. the commit one
   before v2.6.20-rc6 in the kernel repository is:

v2.6.20-rc5-306-ga21b069

which tells you that its object name begins with a21b069,
   v2.6.20-rc5 is an ancestor of it (meaning, the commit
   contains everything -rc5 has), and there are 306 commits
   since v2.6.20-rc5.

- git-describe with --abbrev=0 can be used to show only the
   name of the base ref.

- git-blame learned a new option, --incremental, that tells it
   to output the blames as they are assigned.  A sample script
   to use it is also included as contrib/blameview.

- git-blame starts annotating from the working tree by default.

* Less external dependency

- We no longer require the "merge" program from the RCS suite.
   All 3-way file-level merges are now done internally.

- The original implementation of git-merge-recursive which was
   in Python has been removed; we have a C implementation of it
   now.

- git-shortlog is no longer a Perl script.  It no longer
   requires output piped from git-log; it can accept revision
   parameters directly on the command line.

* I18n

- We have always encouraged the commit message to be encoded in
   UTF-8, but the users are allowed to use legacy encoding as
   appropriate for their projects.  This will continue to be the
   case.  However, a non UTF-8 commit encoding _must_ be
   explicitly set with i18n.commitencoding in the repository
   where a commit is made; otherwise git-commit-tree will
   complain if the log message does not look like a valid UTF-8
   string.

- The value of i18n.commitencoding in the originating
   repository is recorded in the commit object on the "encoding"
   header, if it is not UTF-8.  git-log and friends notice this,
   and re-encodes the message to the log output encoding when
   displaying, if they are different.  The log output encoding
   is determined by "git log --encoding=<encoding>",
   i18n.logoutputencoding configuration, or i18n.commitencoding
   configuration, in the decreasing order of preference, and
   defaults to UTF-8.

- Tools for e-mailed patch application now default to -u
   behavior; i.e. it always re-codes from the e-mailed encoding
   to the encoding specified with i18n.commitencoding.  This
   unfortunately forces projects that have happily been using a
   legacy encoding without setting i18n.commitencoding to set
   the configuration, but taken with other improvement, please
   excuse us for this very minor one-time inconvenience.

* e-mailed patches

- See the above I18n section.

- git-format-patch now enables --binary without being asked.
   git-am does _not_ default to it, as sending binary patch via
   e-mail is unusual and is harder to review than textual
   patches and it is prudent to require the person who is
   applying the patch to explicitly ask for it.

- The default suffix for git-format-patch output is now ".patch",
   not ".txt".  This can be changed with --suffix=.txt option,
   or setting the config variable "format.suffix" to ".txt".

* Foreign SCM interfaces

- git-svn now requires the Perl SVN:: libraries, the
   command-line backend was too slow and limited.

- the 'commit' subcommand of git-svn has been renamed to
   'set-tree', and 'dcommit' is the recommended replacement for
   day-to-day work.

- git fast-import backend.

* User support

- Quite a lot of documentation updates.

- Bash completion scripts have been updated heavily.

- Better error messages for often used Porcelainish commands.

- Git GUI.  This is a simple Tk based graphical interface for
   common Git operations.

* Sliding mmap

- We used to assume that we can mmap the whole packfile while
   in use, but with a large project this consumes huge virtual
   memory space and truly huge ones would not fit in the
   userland address space on 32-bit platforms.  We now mmap huge
   packfile in pieces to avoid this problem.

* Shallow clones

- There is a partial support for 'shallow' repositories that
   keeps only recent history.  A 'shallow clone' is created by
   specifying how deep that truncated history should be
   (e.g. "git clone --depth 5 git://some.where/repo.git").

Currently a shallow repository has number of limitations:

- Cloning and fetching _from_ a shallow clone are not
     supported (nor tested -- so they might work by accident but
     they are not expected to).

- Pushing from nor into a shallow clone are not expected to
     work.

- Merging inside a shallow repository would work as long as a
     merge base is found in the recent history, but otherwise it
     will be like merging unrelated histories and may result in
     huge conflicts.

but this would be more than adequate for people who want to
   look at near the tip of a big project with a deep history and
   send patches in e-mail format.

cmd: