Re: Proposed git mv behavioral change

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

 



El 20/10/2007, a las 8:45, Michael Witten escribió:

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.

I think the issue here is that git-mv as it is currently implemented really conflates two things:

1. Renaming a file in the traditional "mv" sense
2. Staging the entire contents of the file in the index, ready or not

So it's kind of like the command were called git-mv-and-add or git- rename-and-add. And given that the index as a staging area is such a central content in Git, users often want to have more control over what gets added to the index than that; ie. "I really just wanted to rename the file, and leave the staging of modifications to the content up to me".

Cheers,
Wincent



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

  Powered by Linux