Re: How to fork a file (git cp ?)
- From
Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
- Date
- May 5, 2011, 19:27 UTC
- Message-ID
- <BANLkTimPXVosaJBnOEUkURu4nsk=UNtRag@mail.gmail.com>
- In-Reply-To
- <7vk4e56kxa.fsf@alter.siamese.dyndns.org>
On Thu, May 5, 2011 at 8:50 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 11 quoted lines
> Piotr Krukowiecki <piotr.krukowiecki@gmail.com> 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