From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Miklos Vajna <vmiklos@frugalware.org>,
Jakub Narebski <jnareb@gmail.com>,
Matthieu Moy <Matthieu.Moy@imag.fr>,
Francis Moreau <francis.moro@gmail.com>,
git@vger.kernel.org
Subject: Re: [RFC/PATCH] Implement git-cp.
Date: Sun, 10 Feb 2008 14:29:04 +0100 [thread overview]
Message-ID: <200802101429.04765.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <7vzlu9uu7c.fsf@gitster.siamese.dyndns.org>
söndagen den 10 februari 2008 skrev Junio C Hamano:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > If you touch builtin-mv.c already, why not just move cmd_cp() in there?
> > It's not like it would be the first cmd_*() function living in the same
> > file as other cmd_*() functions.
>
> Why do we even want "git-cp", especially when git-mv and git-rm
> are already pretty much redundant commands?
>
> Especially, why do we even encourage copy-and-paste?
We do not. I've seen too much damage being done through copy/paste. A
much better (safer) way to copy code is to re-type it. I've asked more
than once, when asked to help debug a piece of code: "Did you copy this
code?".
For this reason I have a vision of a "plugin" for Eclipse that disables paste
if the clipboard contains copied code. Cut and paste would be ok.
-- robin
next prev parent reply other threads:[~2008-02-10 13:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 18:23 What about git cp ? Francis Moreau
2008-02-03 18:46 ` Matthieu Moy
2008-02-03 19:07 ` Jakub Narebski
2008-02-10 1:12 ` [RFC/PATCH] Implement git-cp Miklos Vajna
2008-02-10 1:26 ` Johannes Schindelin
2008-02-10 7:49 ` Junio C Hamano
2008-02-10 12:33 ` Johannes Schindelin
2008-02-10 12:42 ` Miklos Vajna
2008-02-10 13:29 ` Robin Rosenberg [this message]
2008-02-11 1:30 ` Jakub Narebski
2008-02-11 10:18 ` Matthieu Moy
2008-02-11 13:43 ` Miklos Vajna
2008-02-10 18:24 ` [PATCH] " Miklos Vajna
2008-02-03 18:55 ` What about git cp ? Remi Vanicat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802101429.04765.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=Matthieu.Moy@imag.fr \
--cc=francis.moro@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=vmiklos@frugalware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).