Re: Proposed git mv behavioral change
- From
Michael Witten <mfwitten@mit.edu>
- Date
- Oct 20, 2007, 06:45 UTC
- Message-ID
- <8D972813-2D7F-4D6A-958F-B76E947E7BC3@MIT.EDU>
- In-Reply-To
- <20071020063628.GV14735@spearce.org>
On 20 Oct 2007, at 2:36:28 AM, Shawn O. Pearce wrote:
> Today I move the file, then unstage the hunks I'm not sure about, > then go back and restage them. Annoying. It really disrupts > my workflow.
I know it's against policy, but the proposed change should be set as the default at some point, in my opinion.
Perhaps when the -u flagged is not used, there can be a warning that states -u will become the default at a certain time.
In fact, -u speaks "update" to me, and I would expect it to signal the current behavior.
I have a feeling that my suggestion will not go far, but I also think that backwards compatibility can overstay its welcome.