[email protected] (Alfred M. Szmidt) writes: > No, we should expect people to learn whatever tools are appropriate for > working on the projects they are developing. It's not the place of the > GNU Coding Standards to tell people how to extract particular information > from version control history. And I'd expect most git guides to > concentrate on things such as git bisect, because I'd expect "find the > revision that introduced a bug" to be a more common issue than "find all > changes affecting a symbol called X, across all source files". > > We cannot expect people to learn a multitude of different tools, or > tools that have vanished from history. The above commands might not > even be available in other DVCSs that fall under the critera you > listed, nor are they available under normal usage in for example > Emacs. I know how to use Emacs, I have no intention of learning to > use at least 5 different version control systems, and then expecting > everyone to do so is something that is infact useless and a waste of > time.
how is expecting every developer to do the repetive exercise of describing their changes more productive than teach some lazy users how to use git log/blame? Regards, Giuseppe
