Re: Git log of all (modifying) commands run on a repo?
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Feb 8, 2007, 00:41 UTC
- Message-ID
- <Pine.LNX.4.63.0702080140230.22628@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <7v8xf94hq1.fsf@assigned-by-dhcp.cox.net>
Hi,
On Wed, 7 Feb 2007, Junio C Hamano wrote:
Show 18 quoted lines
> Linus Torvalds <torvalds@linux-foundation.org> writes: > > > With "--pretty=oneline --abbrev-commit" I'll agree that it's actually > > fairly pretty. > > > > Maybe we can make "-g" default to that? As it is, I'd otherwise still use > > "less" just because there is less typing... > > > > Linus > > Well, you would not know if the user gave you '-g' before you > ask setup_revisions() to parse the options, and once you let it > do its thing, you would not know if it also found an explicit > output format given by the end user, so your cannot sanely make > default depend on '-g'. > > I suspect that it would have to be either somewhat involved or > outright hacky.
Well, we could always make CMIT_FMT_DEFAULT _not_be the same as _MEDIUM, and if it still is the same _after_ parsing the options, set it to MEDIUM explicitely. Same goes for the abbrev thing.
Ciao, Dscho