From: "Carlos Martín Nieto" <cmn@elego.de> To: git@vger.kernel.org Cc: gitster@pobox.com Subject: [PATCHv2 0/3] Improve branch UI for setting upstream information Date: Thu, 30 Aug 2012 19:23:10 +0200 [thread overview] Message-ID: <1346347393-8425-1-git-send-email-cmn@elego.de> (raw) Hi all, As a result of making --unset-upstream fail if the given branch doesn't exist, I discovered a copy-paste error in on the the tests in the patch after it, so I'm resending the whole thing. The changes from the last reroll are the tightening of the situations where git will show an error message (not it's just if the branch is new and exists as remote-tracking) which I already sent as a reply in the other thread; and making --unset-upstream error out on bad input, which I already mentioned above. cmn Carlos Martín Nieto (3): branch: introduce --set-upstream-to branch: add --unset-upstream option branch: deprecate --set-upstream and show help if we detect possible mistaken use Documentation/git-branch.txt | 14 ++++++++- builtin/branch.c | 60 +++++++++++++++++++++++++++++++++++++-- t/t3200-branch.sh | 67 ++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 137 insertions(+), 4 deletions(-) -- 1.7.12.3.g0dd8ef6
next reply other threads:[~2012-08-30 17:23 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-30 17:23 Carlos Martín Nieto [this message] 2012-08-30 17:23 ` [PATCH 1/3] branch: introduce --set-upstream-to Carlos Martín Nieto 2012-08-30 17:51 ` Ralf Thielow 2012-08-31 15:22 ` Carlos Martín Nieto 2012-08-31 15:30 ` Ralf Thielow 2012-08-31 17:09 ` Junio C Hamano 2012-09-01 15:13 ` Carlos Martín Nieto 2012-08-30 17:23 ` [PATCH 2/3] branch: add --unset-upstream option Carlos Martín Nieto 2012-08-30 17:23 ` [PATCH 3/3] branch: deprecate --set-upstream and show help if we detect possible mistaken use Carlos Martín Nieto 2012-08-30 17:37 ` [PATCHv2 0/3] Improve branch UI for setting upstream information Junio C Hamano 2012-08-30 18:57 ` Carlos Martín Nieto 2012-08-30 20:12 ` 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=1346347393-8425-1-git-send-email-cmn@elego.de \ --to=cmn@elego.de \ --cc=git@vger.kernel.org \ --cc=gitster@pobox.com \ --subject='Re: [PATCHv2 0/3] Improve branch UI for setting upstream information' \ /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
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.