From: Michael Rappazzo <rappazzo@gmail.com>
To: gitster@pobox.com, sunshine@sunshineco.com, dturner@twopensource.com
Cc: git@vger.kernel.org, Michael Rappazzo <rappazzo@gmail.com>
Subject: [PATCH v9 0/5] worktree: list functions and command
Date: Fri, 2 Oct 2015 07:55:30 -0400 [thread overview]
Message-ID: <1443786935-81131-1-git-send-email-rappazzo@gmail.com> (raw)
Notable changes since v8[1]:
- Rework the commit history to try to better maintain blame
- Use ALLOC_GROW instead of pre-allocating when building the worktree array
- Refine the `--porcelain` format and describe it in the documentation
- Remove whitespace from expected and actual test output
[1]: http://thread.gmane.org/gmane.comp.version-control.git/278190
Michael Rappazzo (5):
worktree: add top-level worktree.c
worktree: refactor find_linked_symref function
worktree: add a function to get worktree details
worktree: add details to the worktree struct
worktree: add 'list' command
Documentation/git-worktree.txt | 49 +++++++++-
Makefile | 1 +
branch.c | 79 +--------------
branch.h | 8 --
builtin/notes.c | 2 +-
builtin/worktree.c | 82 ++++++++++++++++
t/t2027-worktree-list.sh | 89 +++++++++++++++++
worktree.c | 216 +++++++++++++++++++++++++++++++++++++++++
worktree.h | 38 ++++++++
9 files changed, 476 insertions(+), 88 deletions(-)
create mode 100755 t/t2027-worktree-list.sh
create mode 100644 worktree.c
create mode 100644 worktree.h
--
2.6.0
next reply other threads:[~2015-10-02 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 11:55 Michael Rappazzo [this message]
2015-10-02 11:55 ` [PATCH v9 1/5] worktree: add top-level worktree.c Michael Rappazzo
2015-10-02 11:55 ` [PATCH v9 2/5] worktree: refactor find_linked_symref function Michael Rappazzo
2015-10-02 21:16 ` Junio C Hamano
2015-10-02 11:55 ` [PATCH v9 3/5] worktree: add a function to get worktree details Michael Rappazzo
2015-10-02 11:55 ` [PATCH v9 4/5] worktree: add details to the worktree struct Michael Rappazzo
2015-10-02 11:55 ` [PATCH v9 5/5] worktree: add 'list' command Michael Rappazzo
2015-10-02 20:33 ` Junio C Hamano
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=1443786935-81131-1-git-send-email-rappazzo@gmail.com \
--to=rappazzo@gmail.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.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 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).