From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Duy Nguyen <pclouds@gmail.com>
Subject: [PATCH 0/1] Introduce a way to create a branch and worktree at the same time
Date: Thu, 10 Mar 2016 12:34:10 +0100 (CET) [thread overview]
Message-ID: <cover.1457609615.git.johannes.schindelin@gmx.de> (raw)
The invention of the `git worktree` command changed this developer's
working style dramatically. Rather than switching between branches all
the time, topic branches are created and checked out in newly-added
worktrees, to be reworked and refined until the topic branch is either
merged into `master` or abandoned.
It gets rather tiresome, and also typo-prone, to call "git branch xyz
upstream/master && git worktree add xyz xyz" all the time. Hence this
proposal: "git branch -w xyz upstream/master" to do the same.
The plan is to also support "git branch -d -w xyz" once the `git
worktree` command learned a `remove` (or `delete`) subcommand.
One possible improvement would be to add "/xyz/" to the parent
repository's .git/info/exclude, but this developer hesitates to
introduce that feature without the "delete" counterpart: those exclude
entries would likely go stale very quickly. Besides, there might be a
plan in the working to exclude worktrees automagically?
Johannes Schindelin (1):
branch: allow conveniently adding new worktrees for new branches
Documentation/git-branch.txt | 5 +++--
builtin/branch.c | 27 +++++++++++++++++++++++++--
2 files changed, 28 insertions(+), 4 deletions(-)
--
2.7.2.windows.1.8.g47d64e6.dirty
next reply other threads:[~2016-03-10 11:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 11:34 Johannes Schindelin [this message]
2016-03-10 11:34 ` [PATCH 1/1] branch: allow conveniently adding new worktrees for new branches Johannes Schindelin
2016-03-10 11:51 ` [PATCH 0/1] Introduce a way to create a branch and worktree at the same time Duy Nguyen
2016-03-10 11:59 ` Duy Nguyen
2016-03-10 13:24 ` Johannes Schindelin
2016-03-10 13:21 ` Johannes Schindelin
2016-03-11 0:56 ` Duy Nguyen
2016-03-11 6:43 ` Junio C Hamano
2016-03-15 6:53 ` Johannes Schindelin
2016-03-15 10:34 ` Duy Nguyen
2016-03-15 13:56 ` Johannes Schindelin
2016-03-15 14:07 ` Duy Nguyen
2016-03-11 2:57 ` Mikael Magnusson
2016-03-14 13:45 ` Johannes Schindelin
2016-03-15 20:40 ` Johannes Sixt
2016-03-10 20:45 ` Eric Sunshine
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=cover.1457609615.git.johannes.schindelin@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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 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).