git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Techlive Zheng <techlivezheng@gmail.com>
To: git@vger.kernel.org, gitster@pobox.com
Cc: apenwarr@gmail.com, greened@obbligato.org,
	Techlive Zheng <techlivezheng@gmail.com>
Subject: [PATCH/RFC 0/7] mutiple improvements
Date: Sun, 13 Jan 2013 09:52:31 +0800	[thread overview]
Message-ID: <1358041958-1998-1-git-send-email-techlivezheng@gmail.com> (raw)

* refactor tests for 'git subtree'
  * rearrange some tests
  * clean up unnecessary quotes
  * make each test self-contained
* keep commit intact after the split by using '%B'
* handle '--prefix' argument with slash appended correctly

David A. Greene (1):
  contrib/subtree: Remove test number comments

Techlive Zheng (6):
  contrib/subtree: Add vim modeline
  contrib/subtree: Ignore testing directory
  contrib/subtree: Code cleaning and refactoring
  contrib/subtree: Make each test self-contained
  contrib/subtree: Use %B for the split commit message
  contrib/subtree: Handle '--prefix' argument with a slash appended

 contrib/subtree/.gitignore         |    5 +-
 contrib/subtree/git-subtree.sh     |   83 ++-
 contrib/subtree/git-subtree.txt    |   13 +
 contrib/subtree/t/t7900-subtree.sh | 1233 +++++++++++++++++++++++-------------
 4 files changed, 872 insertions(+), 462 deletions(-)

-- 
1.8.1

             reply	other threads:[~2013-01-13  1:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-13  1:52 Techlive Zheng [this message]
2013-01-13  1:52 ` [PATCH/RFC 1/7] contrib/subtree: Add vim modeline Techlive Zheng
2013-01-13  1:52 ` [PATCH/RFC 2/7] contrib/subtree: Ignore testing directory Techlive Zheng
2013-01-13  1:52 ` [PATCH/RFC 3/7] contrib/subtree: Remove test number comments Techlive Zheng
2013-01-13  1:52 ` [PATCH/RFC 4/7] contrib/subtree: Code cleaning and refactoring Techlive Zheng
2013-01-14  3:30   ` 郑文辉(Techlive Zheng)
2013-01-13  1:52 ` [PATCH/RFC 5/7] contrib/subtree: Make each test self-contained Techlive Zheng
2013-01-13  1:52 ` [PATCH/RFC 6/7] contrib/subtree: Use %B for the split commit message Techlive Zheng
2013-01-13  1:52 ` [PATCH/RFC 7/7] contrib/subtree: Handle '--prefix' argument with a slash appended Techlive Zheng
2013-01-14  3:52 ` [PATCH/RFC v2 0/8] contrib/subtree: Reroll to follow Git's whitespace policy Techlive Zheng
2013-01-14  3:52   ` [PATCH/RFC v2 1/8] contrib/subtree: Fix whitespaces Techlive Zheng
2013-01-14  3:52   ` [PATCH/RFC v2 2/8] contrib/subtree: Add vim modeline Techlive Zheng
2013-01-14  3:52   ` [PATCH/RFC v2 3/8] contrib/subtree: Ignore testing directory Techlive Zheng
2013-01-14  3:52   ` [PATCH/RFC v2 4/8] contrib/subtree: Remove test number comments Techlive Zheng
2013-01-14  3:52   ` [PATCH/RFC v2 5/8] contrib/subtree: Code cleaning and refactoring Techlive Zheng
2013-01-14  3:52   ` [PATCH/RFC v2 6/8] contrib/subtree: Make each test self-contained Techlive Zheng
2013-01-14  3:52   ` [PATCH/RFC v2 7/8] contrib/subtree: Use %B for the split commit message Techlive Zheng
2013-01-14  3:52   ` [PATCH/RFC v2 8/8] contrib/subtree: Handle '--prefix' argument with a slash appended Techlive Zheng

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=1358041958-1998-1-git-send-email-techlivezheng@gmail.com \
    --to=techlivezheng@gmail.com \
    --cc=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=greened@obbligato.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).