From: "Rubén Justo" <rjusto@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH v2 0/2] branch: support for shortcuts like @{-1}, completed
Date: Wed, 7 Sep 2022 11:45:36 +0200 [thread overview]
Message-ID: <93b0b442-b277-66a6-3f5f-5a498593aa07@gmail.com> (raw)
In-Reply-To: <pull.1346.git.1662388460.gitgitgadget@gmail.com>
branch options: "edit-description", "set-upstream-to" and "unset-upstream"
don't handle shortcuts like @{-1}.
This patch address this problem.
In v2 I've resolved some noise in the code, aggregated two tests in one with
some refactoring to do the test in a more simple way while covering the
functionality. Also changed the commit messages to better explain and
document the change.
Thanks
Rubén Justo (2):
branch: refactor "edit_description" code path
branch: support for shortcuts like @{-1} completed
builtin/branch.c | 46 ++++++++++++++++++---------
t/t3204-branch-name-interpretation.sh | 25 +++++++++++++++
2 files changed, 56 insertions(+), 15 deletions(-)
base-commit: 795ea8776befc95ea2becd8020c7a284677b4161
Range-diff vs v1:
1: aaa2f3ec31 ! 1: ce14194187 branch: refactor edit_description command switch case
@@ Metadata
Author: Rubén Justo <rjusto@gmail.com>
## Commit message ##
- branch: refactor edit_description command switch case
+ branch: refactor "edit_description" code path
- Minor refactoring to reduce the return exits in the switch case
- handling the edit_description command, so the calls to strbuf_release
- can also be reduced.
+ Minor refactoring to reduce the number of returns in the switch case
+ handling the "edit_description" option, so the calls to strbuf_release
+ can also be reduced. New resources to be added also do not need to be
+ released in multiple places.
Signed-off-by: Rubén Justo <rjusto@gmail.com>
2: 321854e118 ! 2: 3a591cab8a branch: support for at-refs like @{-1}
@@ Metadata
Author: Rubén Justo <rjusto@gmail.com>
## Commit message ##
- branch: support for at-refs like @{-1}
+ branch: support for shortcuts like @{-1} completed
- branch command with --edit-description, --set-upstream-to and
- --unset-upstream options expects a branch name. A branch can be
- specified using at-refs like @{-1}, so those references need to
- be resolved.
+ branch command with options "edit-description", "set-upstream-to"
+ and "unset-upstream" expects a branch name. Since ae5a6c3684
+ (checkout: implement "@{-N}" shortcut name for N-th last branch,
+ 2009-01-17) a branch can be specified using shortcuts like @{-1}.
+ Those shortcuts need to be resolved when considering the
+ arguments.
+
+ Usage examples:
We can modify the description of the previously checked out branch
with:
@@ builtin/branch.c: int cmd_branch(int argc, const char **argv, const char *prefix
+ else if (argc == 1) {
+ strbuf_branchname(&buf, argv[0], INTERPRET_BRANCH_LOCAL);
+ branch = branch_get(buf.buf);
-+ }
-+ else
++ } else
die(_("too many arguments to set new upstream"));
-+
if (!branch) {
- if (!argc || !strcmp(argv[0], "HEAD"))
- die(_("could not set upstream of HEAD to %s when "
@@ builtin/branch.c: int cmd_branch(int argc, const char **argv, const char *prefix)
dwim_and_setup_tracking(the_repository, branch->name,
new_upstream, BRANCH_TRACK_OVERRIDE,
@@ builtin/branch.c: int cmd_branch(int argc, const char **argv, const char *prefix
+ else if (argc == 1) {
+ strbuf_branchname(&buf, argv[0], INTERPRET_BRANCH_LOCAL);
+ branch = branch_get(buf.buf);
-+ }
-+ else
++ } else
die(_("too many arguments to unset upstream"));
if (!branch) {
@@ t/t3204-branch-name-interpretation.sh: test_expect_success 'checkout does not tr
+ test_cmp expect EDITOR_OUTPUT
+'
+
-+test_expect_success 'modify branch upstream via "@{-1}@{upstream}"' "
-+ cat >expect <<-\EOF &&
-+ warning: not setting branch 'upstream-branch' as its own upstream
-+ EOF
++test_expect_success 'modify branch upstream via "@{-1}" and "@{-1}@{upstream}"' '
+ git branch upstream-branch &&
+ git checkout -b upstream-other -t upstream-branch &&
+ git checkout - &&
-+ git branch --set-upstream-to upstream-branch @{-1}@{upstream} 2>actual &&
-+ test_cmp expect actual
-+"
-+
-+test_expect_success 'unset branch upstream via "@{-1}"' "
-+ test "$(git config branch.upstream-other.remote)" = "." &&
-+ test "$(git config branch.upstream-other.merge)" = "refs/heads/upstream-branch" &&
-+ git checkout upstream-other &&
-+ git checkout - &&
++ git branch --set-upstream-to @{-1} @{-1}@{upstream} &&
++ test "$(git config branch.upstream-branch.merge)" = "refs/heads/upstream-other" &&
+ git branch --unset-upstream @{-1} &&
-+ test_must_fail git config branch.upstream-other.remote &&
+ test_must_fail git config branch.upstream-other.merge
-+"
++'
+
test_done
--
2.36.1
next prev parent reply other threads:[~2022-09-07 9:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 14:34 [PATCH 0/2] branch: support for at-refs like @{-1} in --edit-description, --set-upstream-to and --unset-upstream Rubén Justo via GitGitGadget
2022-09-05 14:34 ` [PATCH 1/2] branch: refactor edit_description command switch case Rubén Justo via GitGitGadget
2022-09-05 14:34 ` [PATCH 2/2] branch: support for at-refs like @{-1} Rubén Justo via GitGitGadget
2022-09-07 9:45 ` Rubén Justo [this message]
2022-09-07 9:52 ` [PATCH v2 1/2] branch: refactor "edit_description" code path Rubén Justo
2022-09-07 20:25 ` Junio C Hamano
2022-09-07 21:24 ` Rubén Justo
2022-09-08 4:32 ` Rubén Justo
2022-09-07 9:53 ` [PATCH v2 2/2] branch: support for shortcuts like @{-1} completed Rubén Justo
2022-09-08 4:47 ` [PATCH v3 0/2] branch: support for shortcuts like @{-1}, completed Rubén Justo
2022-09-08 4:51 ` [PATCH v3 1/2] branch: refactor "edit_description" code path Rubén Justo
2022-09-08 20:57 ` [PATCH] branch: error codes for "edit_description" Rubén Justo
2022-09-08 21:45 ` Junio C Hamano
2022-09-08 4:53 ` [PATCH v3 2/2] branch: support for shortcuts like @{-1} completed Rubén Justo
2022-10-08 1:00 ` [PATCH v4] branch: support for shortcuts like @{-1}, completed Rubén Justo
2022-10-08 3:17 ` Eric Sunshine
2022-10-08 4:23 ` Junio C Hamano
2022-10-08 7:07 ` Rubén Justo
2022-10-08 7:23 ` Eric Sunshine
2022-10-08 9:12 ` Rubén Justo
2022-10-08 17:10 ` Eric Sunshine
2022-10-08 17:46 ` Junio C Hamano
2022-10-08 20:48 ` Rubén Justo
2022-10-08 23:28 ` Rubén Justo
2022-10-09 6:46 ` Eric Sunshine
2022-10-09 19:33 ` Junio C Hamano
2022-10-09 22:27 ` Rubén Justo
2022-10-08 4:17 ` Junio C Hamano
2022-10-08 9:04 ` Rubén Justo
2022-10-08 22:32 ` [PATCH v5] " Rubén Justo
2022-10-09 5:37 ` Junio C Hamano
2022-10-09 19:11 ` Junio C Hamano
2022-10-09 21:26 ` Rubén Justo
2022-10-10 0:38 ` Junio C Hamano
2022-10-10 6:05 ` Rubén Justo
2022-10-10 16:55 ` Junio C Hamano
2022-10-10 18:08 ` Rubén Justo
2022-10-10 23:24 ` [PATCH v6] " Rubén Justo
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93b0b442-b277-66a6-3f5f-5a498593aa07@gmail.com \
--to=rjusto@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).