Re: Proposed git mv behavioral change
On 18 Oct 2007, at 11:47:05 PM, Jeff King wrote:
Show 10 quoted lines
> The only workflow I can think of is:
>
> 1. you modify a.c
> 2. your boss comes in and tells you to make some unrelated change,
> which involves moving a.c to b.c
> 3. You don't want to commit your changes, so you git-mv in the index
> only without involving your dirty working tree file.
> 4. You commit the index (which doesn't have your changes from (1)
>
> I think that is sort of a bogus workflow
Ha!
That's exactly what the original poster wanted.
It's not unreasonable.
Michael Witten <mfwitten@mit.edu>