From: Jakub Narebski <jnareb@gmail.com>
To: Guanqun Lu <guanqun.lu@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] add test-dump-cache-tree in Makefile
Date: Wed, 04 Feb 2009 01:31:32 -0800 (PST) [thread overview]
Message-ID: <m34ozawnte.fsf@localhost.localdomain> (raw)
In-Reply-To: <1233781241-721-2-git-send-email-guanqun.lu@gmail.com>
Guanqun Lu <guanqun.lu@gmail.com> writes:
> dump-cache-tree.c | 64 ------------------------------------------------
> test-dump-cache-tree.c | 64 ++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 65 insertions(+), 64 deletions(-)
> delete mode 100644 dump-cache-tree.c
> create mode 100644 test-dump-cache-tree.c
> diff --git a/dump-cache-tree.c b/dump-cache-tree.c
> deleted file mode 100644
> index 1f73f1e..0000000
> diff --git a/test-dump-cache-tree.c b/test-dump-cache-tree.c
> new file mode 100644
> index 0000000..1f73f1e
Minor nit: it would be better to use git-format-patch with '-M' option
(detect renames) here. It would result in shorter and more readable
patch:
dump-cache-tree.c => test-dump-cache-tree.c | 0
3 files changed, 1 insertions(+), 0 deletions(-)
rename dump-cache-tree.c => test-dump-cache-tree.c (100%)
diff --git a/dump-cache-tree.c b/test-dump-cache-tree.c
similarity index 100%
rename from dump-cache-tree.c
rename to test-dump-cache-tree.c
Or something like that...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-02-04 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 21:00 [PATCH 1/2] fix typo in Documentation Guanqun Lu
2009-02-04 5:30 ` Sverre Rabbelier
2009-02-04 9:26 ` Jakub Narebski
2009-02-05 6:27 ` Guanqun Lu
2009-02-04 21:00 ` [PATCH 2/2] add test-dump-cache-tree in Makefile Guanqun Lu
2009-02-04 7:46 ` Junio C Hamano
2009-02-04 9:31 ` Jakub Narebski [this message]
2009-02-06 13:43 ` [PATCH 1/2] fix typo in Documentation Mikael Magnusson
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=m34ozawnte.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=guanqun.lu@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.