From: "Aaron Gray" <angray@beeb.net>
To: "VMiklos" <vmiklos@frugalware.org>
Cc: <git@vger.kernel.org>
Subject: Re: renaming question
Date: Mon, 20 Aug 2007 03:40:24 +0100 [thread overview]
Message-ID: <04a501c7e2d3$75c26740$0600a8c0@ze4427wm> (raw)
In-Reply-To: 20070820021109.GB768@genesis.frugalware.org
Hello,
>Na Sun, Aug 19, 2007 at 07:32:01PM +0100, Aaron Gray <angray@beeb.net>
>pisal(a):
>> rename test.c test.cpp *
>> vi test.cpp
>> git rm test.c
>> git add test.cpp
>or just git mv test.c test.cpp
Yes I gathered that.
followed by 'vi test.cpp' :)
GIT's looking great, cannot wait to really start using it.
Aaron
prev parent reply other threads:[~2007-08-20 2:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 17:58 renaming question Aaron Gray
2007-08-19 18:16 ` Florian Weimer
2007-08-19 18:32 ` Aaron Gray
2007-08-19 19:05 ` David Kastrup
2007-08-19 19:17 ` Aaron Gray
2007-08-19 19:49 ` David Kastrup
2007-08-19 20:37 ` Florian Weimer
2007-08-20 0:45 ` Steven Grimm
2007-08-20 1:30 ` Aaron Gray
2007-08-20 1:56 ` Shawn O. Pearce
2007-08-20 2:11 ` VMiklos
2007-08-20 2:40 ` Aaron Gray [this message]
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='04a501c7e2d3$75c26740$0600a8c0@ze4427wm' \
--to=angray@beeb.net \
--cc=git@vger.kernel.org \
--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).