Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [RFC/PATCH 0/2] Documentation: kicking the "reset --hard" habit

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:49:57

Matthieu Moy [off-list ref] writes:
Jonathan Nieder [off-list ref] writes:
quoted
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?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help