Re: How to fork a file (git cp ?)

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

 



On Thu, May 5, 2011 at 8:50 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> Piotr Krukowiecki <piotr.krukowiecki@xxxxxxxxx> writes:
>
>> Maybe Mikhail wanted to say that if there's a git-mv as a shortcut for
>>   "cp old new ; rm old; add new"
>> then there should be a git-cp as a shortcut for
>>   "cp old new; add new"
>
> Copying and then futzing with a copy is a bad discipline to begin with.
> git already has a reputation of having too many commands.  I am not
> thrilled about the idea of making things worse by adding an unnecessary
> command, and especially one that encourages a bad workflow.

I'm not saying I want to have git-cp, but could you explain what is wrong with
"cp old new; add new" (why is that bad workflow? How come adding a copy
of a file can be a workflow at all?)


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