Konstantin Khomoutov schreef op 12-08-2016 19:54:
Depend on what you're asking for.
If you have asked about the `git log`, then yes: have an alias like
git config --add --global alias.rlog `log -M -C`
If you have asked about whether it's possible to change the way Git
stores the history, then the answer is no.
As usually, I'd urge you to read an extensive overview of why Git
manages information in the way it does provided by its very creator
[1].
While you certainly may disagree on the points made there and/or with
the conclusions drawn, it helps in acquiring the correct perspective:
in
that text, some interesting areas are covered -- such as obtaining the
same information from several sources in an (octopus) merge or patches
-- things most of us never deal with. What I'm leading to, is that Git
was created not as an academic project to create some idealized VC
system tailored for no particular real-world case, and implementing
whatever seemed "sensible" for a VC system to do.
Well, I don't care too much about other people's opinions or what they
think should be the proper use case for a certain system, after all, my
particular question was not at all of the academic kind, but pertained
to a particular use case of being able to easily perceive the history of
a file, in the sense of knowing where it came from and what has happened
to it. I know (now) there are Git tools that will show me this
information, likely.
I am not concerned with changing the internals of Git. If, as you say,
Git is perfectly capable of piecing together the "real" history of a
file without actually storing that information (directly), then from a
practical point of view it shouldn't matter all that much, as long as it
is usable and accessible.
I am sure the philosophical underpinnings of Git are quite proficient,
including its fundamental "efficiency" model so to speak. But I don't
need to know abut them today (maybe later).
First comes a use case and automated tools are fine but many of the
higher level Git commands are not easy to use and take a while to put
them into your system where you have all these aliases; and any system
with a lot of aliases that are actually quite required in order for the
system to be useful really increase the scope of the commitment you must
have to the system in the first place.
The short way of saying that is that defaults matter, of course.
So today for me this question was really about: what do real people,
regular people, do, when they are discontent with the level of
information that is usually shown, and what would be their best
practices in showing that.
I will attempt Git -M -C next time I use it, thank you.
The problem I have constantly is that I am "very bad at" saving all of
these customizations so I have to reapply them each time I install a new
system, so to speak, quite literally.
This just puts a bigger burden onto the usability of the system because
those "customizations" are pretty much required for a proper use of the
system, I feel, and this "developmental investment" is something you
need to save.
I haven't been able to do so very well thus far, usually. They weren't
important enough but still bite you when you don't have them :-/.
1. http://www.gelato.unsw.edu.au/archives/git/0504/0598.html
Thank you for the long text you wrote anway, relatively speaking, very
few people take the time to write anything as thorough or complete like
that, or anything of that kind.
So again, I do appreciate you taking the time to write that.
It's just that git is a bit of a git at times ;-). (As per the words of
Mister Torvalds himself, I guess).
Regards :).
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
