On 9/23/07, Junio C Hamano [off-list ref] wrote:
Lars Hjemli [off-list ref] writes:
quoted
This option can be used to override --no-commit and --squash. The change
also introduces slightly different behavior for --no-commit: when specified,
it explicitly overrides --squash.
Makes me wonder if --no-squash also make sense to override a --squash.
Is this really needed? IOW, does it ever make sense to have --no-commit
in the configuration?
Actually, I did add --no-squash but the semantics (and implementation)
was identical to --commit so I decided it wasn't worth it (but maybe
it is - just to avoid user confusion?).
--
larsh