Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> writes: > Jonathan Nieder <jrnieder@xxxxxxxxx> writes: > >> Sadly, at least the user manual change suggested below is probably >> not suitable, since reset --keep and --merge have not been around >> since git 1.5.3 days. Ideas for working around that and other >> comments would be welcome. > > Do we really want to keep the user manual compatible with 1.5.3 > forever? It's nice to keep the user manual usable by slightly outdated > Gits, but 1.5.3 starts being really old,... 1.5.6 is more than 2 years old (June 18th, 2008), 1.5.3 is more than 3 years old (September 2nd, 2007). In git timescale, they are becoming prehistoric. Even though the knowledge of the conceptual structure and the philosophy learned with old versions like 1.5.X series would still apply to today's git, at the UI level facing the end users, there are vast differences (some may call that improvements ;-) between them and today's git. I am tempted to say we should 1.5.X series behind, and name one that is still relatively old like 1.6.3 (May 2009) or 1.6.4 (July 2009) the oldest vintage we currently recognise as a proper member of our family. What is the oldest version of git that is shipped with _current_ distros, by the way? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html