From: Zack Brown <zbrown@tumblerings.org>
To: Git Mailing List <git@vger.kernel.org>
Subject: cg-mv
Date: Fri, 7 Oct 2005 07:33:33 -0700 [thread overview]
Message-ID: <20051007143333.GA18843@tumblerings.org> (raw)
Hi,
IIRC, file renaming is something we only care about at read time, we don't
actually need to track it while making the change, because git allows us to
track data from file to file without having to tell it that the data is moving.
So, just to keep certain people happy, why not have the cg-mv command defined to
something like this:
#!/bin/bash
cp $1 $2
cg-rm $1
cg-add $2
Be well,
Zack
--
Zack Brown
next reply other threads:[~2005-10-07 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 14:33 Zack Brown [this message]
2005-10-12 10:07 ` cg-mv Petr Baudis
2005-10-12 13:14 ` cg-mv Josef Weidendorfer
2005-10-12 14:28 ` cg-mv] Zack Brown
2005-10-12 22:32 ` cg-mv Horst von Brand
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=20051007143333.GA18843@tumblerings.org \
--to=zbrown@tumblerings.org \
--cc=git@vger.kernel.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