From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: A couple branch questions
Date: Wed, 13 Feb 2008 20:39:56 -0500 [thread overview]
Message-ID: <76718490802131739n22c56cadn39c1871ea1762dc3@mail.gmail.com> (raw)
1) git-branch -d <branchname> complains if <branchname> hasn't been
merged to HEAD. Shouldn't it really only complain if <branchname>
hasn't been merged into any local branch? i.e., as long as
<branchname> has been merged, why care to which branch?
2) Why does --track work only for remote tracking branches? I think it
would be useful for setting up topic branches. I've actually got this
alias setup, but maybe a --topic option for git-checkout and
git-branch would be useful to others (?):
topic = "!sh -c 'branch=$(git symbolic-ref HEAD); test -n \"$branch\"
&& git co -b \"$1\" && git config branch.\"$1\".merge \"$branch\" &&
git config branch.\"$1\".remote . && git config branch.\"$1\".rebase
true' -"
j.
next reply other threads:[~2008-02-14 1:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 1:39 Jay Soffian [this message]
2008-02-14 1:45 ` A couple branch questions David Symonds
2008-02-14 2:24 ` Bill Lear
2008-02-14 3:03 ` David Symonds
2008-02-14 3:43 ` Junio C Hamano
2008-02-14 14:01 ` Keeping reflogs on branch deletion Brian Downing
2008-02-14 15:00 ` Nicolas Pitre
2008-02-14 15:08 ` Johannes Schindelin
2008-02-14 15:17 ` Jeff King
2008-02-14 16:16 ` Nicolas Pitre
2008-02-14 16:31 ` Jeff King
2008-02-14 17:32 ` Nicolas Pitre
2008-02-14 17:57 ` Jeff King
2008-02-14 20:17 ` Wincent Colaiuta
2008-02-14 16:35 ` Jakub Narebski
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=76718490802131739n22c56cadn39c1871ea1762dc3@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.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).