On 9/23/07, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Lars Hjemli <hjemli@xxxxxxxxx> writes: > > > 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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
