Re: [PATCH] Changed timestamp behavior of options -c/-C/--amend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




So my suspicion is that there are some people who almost always want
--new-timestamp, and some people who almost always want --old-timestamp,
depending on their usual workflow. In which case a config option
probably makes the most sense (but keeping the command-line to override
the config, of course).

I'd say the config option should be per-branch (so that you can set the old-timestamp option only in integration branches, and not in topic branches), and that with such an option you could make the default be --new-timestamp in all three cases.

Paolo

--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]