All of lore.kernel.org
 help / color / mirror / Atom feed
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 v8 0/4] worktree: list functions and command
Date: Fri, 18 Sep 2015 09:30:23 -0400	[thread overview]
Message-ID: <1442583027-47653-1-git-send-email-rappazzo@gmail.com> (raw)

Changes from v7[1]:

	- Reworked history to try to maintain blame from moving functions 
	  from branch.c

	- Removed the worktree_list struct (linked list) and instead return
	  return an array of worktrees.  An alternative was also proposed to
	  include a `next` pointer in the worktree struct.  I coded this 
	  option separately (found in my github fork[2]), but ultimately felt
	  that the array was more managable from a client perspective.

	- Removed the `--skip-bare` and `--verbose` command line options for 
	  `worktree list`.

	- The default output of the includes all of the details which were
	  previously only included in verbose output.  Sample output:

		$git worktree list
		/Users/me/code/bare-git-source         (bare)
		/Users/me/code/worktree-git-from-bare  7ecec52 [master]
		/Users/me/code/wt2                     8681989 (detached HEAD)

	- Added `--porcelain` option to the worktree list command.  

		$git worktree list --porcelain
		worktree /Users/mike/code/bare-git-source
		bare
		
		worktree /Users/mike/code/worktree-git-from-bare
		branch master
		
		worktree /Users/mike/code/wt2
		detached at 8681989

[1]: http://thread.gmane.org/gmane.comp.version-control.git/277335
[2]: https://github.com/git/git/compare/master...rappazzo:worktree-list/v8/next-entry-in-worktree

Michael Rappazzo (4):
  worktree: add top-level worktree.c
  worktree: refactor find_linked_symref function
  worktree: add functions to get worktree details
  worktree: add 'list' command

 Documentation/git-worktree.txt |  15 ++-
 Makefile                       |   1 +
 branch.c                       |  79 +-------------
 branch.h                       |   8 --
 builtin/notes.c                |   1 +
 builtin/worktree.c             |  78 ++++++++++++++
 t/t2027-worktree-list.sh       |  86 +++++++++++++++
 worktree.c                     | 238 +++++++++++++++++++++++++++++++++++++++++
 worktree.h                     |  38 +++++++
 9 files changed, 457 insertions(+), 87 deletions(-)
 create mode 100755 t/t2027-worktree-list.sh
 create mode 100644 worktree.c
 create mode 100644 worktree.h

-- 
2.5.0

             reply	other threads:[~2015-09-18 13:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 13:30 Michael Rappazzo [this message]
2015-09-18 13:30 ` [PATCH v8 1/4] worktree: add top-level worktree.c Michael Rappazzo
2015-09-22 17:16   ` Junio C Hamano
2015-09-18 13:30 ` [PATCH v8 2/4] worktree: refactor find_linked_symref function Michael Rappazzo
2015-09-22 17:44   ` Junio C Hamano
2015-09-18 13:30 ` [PATCH v8 3/4] worktree: add functions to get worktree details Michael Rappazzo
2015-09-22 18:10   ` Junio C Hamano
2015-09-18 13:30 ` [PATCH v8 4/4] worktree: add 'list' command Michael Rappazzo
2015-09-22 19:42   ` Junio C Hamano
2015-09-24  2:58     ` Mike Rappazzo
2015-09-24  5:00       ` 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=1442583027-47653-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 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.