From: "Carlos Martín Nieto" <cmn@elego.de>
To: git@vger.kernel.org
Subject: [PATCH 0/3] Improve branch UI for setting upstream information
Date: Mon, 20 Aug 2012 15:47:37 +0200 [thread overview]
Message-ID: <1345470460-28734-1-git-send-email-cmn@elego.de> (raw)
Hi all,
After way too long, here's the next iteration of the concept that
began with swapping arguments in --set-upstream like -m does.
After the feedback from the list, --set-upstream-to was born and
--set-upstream is being deprecated in favour of either --track or
--set-upstream-to depening on which of the behaviours the user wants
to have.
Using --set-upsteam with one argument now also leads to a message
explaining how to undo it. For that, branch has learnt
--unset-upstream which will remove the upstream information for the
given branch (or HEAD).
Carlos Martín Nieto (3):
branch: introduce --set-upstream-to
branch: add --unset-upstream option
branch: suggest how to undo a --set-upstream when given one branch
Documentation/git-branch.txt | 14 +++++++-
builtin/branch.c | 65 +++++++++++++++++++++++++++++++++--
t/t3200-branch.sh | 82 ++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 157 insertions(+), 4 deletions(-)
--
1.7.11.1.104.ge7b44f1
next reply other threads:[~2012-08-20 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 13:47 Carlos Martín Nieto [this message]
2012-08-20 13:47 ` [PATCH 1/3] branch: introduce --set-upstream-to Carlos Martín Nieto
2012-08-20 13:47 ` [PATCH 2/3] branch: add --unset-upstream option Carlos Martín Nieto
2012-08-23 21:20 ` Junio C Hamano
2012-08-27 17:30 ` Carlos Martín Nieto
2012-08-27 18:01 ` Junio C Hamano
2012-08-27 18:14 ` Junio C Hamano
2012-08-27 21:33 ` Carlos Martín Nieto
2012-08-20 13:47 ` [PATCH 3/3] branch: suggest how to undo a --set-upstream when given one branch Carlos Martín Nieto
2012-08-20 18:50 ` Junio C Hamano
2012-08-22 1:26 ` Carlos Martín Nieto
2012-08-23 18:56 ` [PATCHv2 3/3] branch: deprecate --set-upstream and show help if we detect possible mistaken use Carlos Martín Nieto
2012-08-23 21:16 ` 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=1345470460-28734-1-git-send-email-cmn@elego.de \
--to=cmn@elego.de \
--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).