On 02/13/2011 03:50 PM, Reinier Zwitserloot wrote:
The commits you lose are the same commits you lose if you use hg squash.
On git you don't lose those commits either, in fact - they are still
in the reflog for 3 months. If after 3 months and a gc (i.e. actively
developing) you notice a problem, then I rather doubt poking around in
the almost random crud that represented 'savegames' is going to be of
so much help that its worth having to drudge through all that stuff
everytime you delve into the repo to check history of anything else.
I pretty much agree with Ricky that keeping every bit of history is
interesting for this reason: simply told, either you do something which
has a meaning, or something which doesn't. If it has a meaning, you keep
it. If it doesn't you keep the memory of it so in one year, when you've
forgotten about it or somebody else steps into the project, you can
precisely recall why it didn't have a meaning.
(Not to add that sometimes things that don't have a meaning suddenly get
it after a few time and a change in the context).
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
fabrizio.giud...@tidalwave.it
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to javaposse@googlegroups.com.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
