home | list info | list archive | date index | thread index

[OCLUG-Tech] what does git not do *easily* you shouldn't be doing anyway?

  • Subject: [OCLUG-Tech] what does git not do *easily* you shouldn't be doing anyway?
  • From: "Robert P. J. Day" <rpjday [ at ] crashcourse [ dot ] ca>
  • Date: Wed, 28 Sep 2016 04:48:15 -0400 (EDT)
  prepping for delivering upcoming git courses, and i'm adding a short
page for questions i get on a regular basis along the lines of "how do
you do X in git?" when, for the most part, i typically answer, "why
would you want to do that in the first place?"

  unsurprisingly, it's fairly common for folks from another VCS to
have done some operation regularly over the years, then they're
surprised that there's no *simple* way to do that in git, and they get
all bent out of shape, even though they can't really defend the need
to do such an operation.

  perfect example: "how do i find the Nth last version of a file?"
now, you can certainly do this in git, using "git log", then extract
the commit ID from the appropriate line and so on. but (AFAIK), there
is no single command to get that info. and, as i said, i'm not sure
why people *need* that sort of info.

  in any event, any thoughts on the sorts of things people do with
other VCSes for which there is no immediate git counterpart, but for
which there is no comprehensible need to do that in the first place?



Robert P. J. Day                                 Ottawa, Ontario, CANADA

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday