From: Jonathan Nieder <jrnieder@gmail.com> To: "Carlos Martín Nieto" <cmn@elego.de> Cc: git@vger.kernel.org, gitster@pobox.com, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> Subject: Re: [PATCH 1/3] branch: introduce --set-upstream-to Date: Tue, 10 Jul 2012 14:13:54 -0500 [thread overview] Message-ID: <20120710191354.GE8439@burratino> (raw) In-Reply-To: <1341939181-8962-2-git-send-email-cmn@elego.de> Hi, Carlos Martín Nieto wrote: > The existing --set-uptream option can cause confusion, as it uses the > usual branch convention of assuming a starting point of HEAD if none > is specified, causing > > git branch --set-upstream origin/master > > to create a new local branch 'origin/master' that tracks the current > branch. As --set-upstream already exists, we can't simply change its > behaviour. To work around this, introduce --set-upstream-to which > accepts a compulsory argument Thanks. A part of me really dislikes this --set-upstream-to which is named more awkwardly than the deprecated mistake it replaces, though. Here's a patch on top to play with that names the new option "--set-upstream=". Untested. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> --- diff --git i/Documentation/git-branch.txt w/Documentation/git-branch.txt index f572913f..57935a64 100644 --- i/Documentation/git-branch.txt +++ w/Documentation/git-branch.txt @@ -49,7 +49,7 @@ branch so that 'git pull' will appropriately merge from the remote-tracking branch. This behavior may be changed via the global `branch.autosetupmerge` configuration flag. That setting can be overridden by using the `--track` and `--no-track` options, and -changed later using `git branch --set-upstream-to`. +changed later using `git branch --set-upstream`. With a `-m` or `-M` option, <oldbranch> will be renamed to <newbranch>. If <oldbranch> had a corresponding reflog, it is renamed to match @@ -174,11 +174,13 @@ start-point is either a local or remote-tracking branch. like `--track` would when creating the branch, except that where branch points to is not changed. --u <upstream>:: ---set-upstream-to=<upstream>:: +--set-upstream=<upstream>:: Set up <branchname>'s tracking information so <upstream> is considered <branchname>'s upstream branch. If no branch is specified it defaults to the current branch. ++ +If no argument is attached, for historical reasons the meaning is +different. See above. --edit-description:: Open an editor and edit the text to explain what the branch is diff --git i/builtin/branch.c w/builtin/branch.c index c886fc06..0d705790 100644 --- i/builtin/branch.c +++ w/builtin/branch.c @@ -669,6 +669,31 @@ static int opt_parse_merge_filter(const struct option *opt, const char *arg, int return 0; } +struct set_upstream_params { + enum branch_track *track; + const char **new_upstream; +}; +static int parse_opt_set_upstream(const struct option *opt, const char *arg, int unset) +{ + struct set_upstream_params *o = opt->value; + + if (unset) { /* --no-set-upstream */ + *o->track = BRANCH_TRACK_NEVER; + *o->new_upstream = NULL; + return 0; + } + + *o->track = BRANCH_TRACK_OVERRIDE; + if (!arg) /* --set-upstream <branchname> <start-point> */ + *o->new_upstream = NULL; + else /* --set-upstream=<upstream> <branchname> */ + *o->new_upstream = arg; + return 0; +} +#define OPT_SET_UPSTREAM(s, l, v) \ + { OPTION_CALLBACK, (s), (l), (v), "upstream", "change upstream info", \ + PARSE_OPT_OPTARG, &parse_opt_set_upstream } + static const char edit_description[] = "BRANCH_DESCRIPTION"; static int edit_branch_description(const char *branch_name) @@ -716,6 +741,7 @@ int cmd_branch(int argc, const char **argv, const char *prefix) const char *new_upstream = NULL; enum branch_track track; int kinds = REF_LOCAL_BRANCH; + struct set_upstream_params set_upstream_args = { &track, &new_upstream }; struct commit_list *with_commit = NULL; struct option options[] = { @@ -725,9 +751,7 @@ int cmd_branch(int argc, const char **argv, const char *prefix) OPT__QUIET(&quiet, "suppress informational messages"), OPT_SET_INT('t', "track", &track, "set up tracking mode (see git-pull(1))", BRANCH_TRACK_EXPLICIT), - OPT_SET_INT( 0, "set-upstream", &track, "change upstream info", - BRANCH_TRACK_OVERRIDE), - OPT_STRING('u', "set-upstream-to", &new_upstream, "upstream", "change the upstream info"), + OPT_SET_UPSTREAM(0, "set-upstream", &set_upstream_args), OPT__COLOR(&branch_use_color, "use colored output"), OPT_SET_INT('r', "remotes", &kinds, "act on remote-tracking branches", REF_REMOTE_BRANCH),
next prev parent reply other threads:[~2012-07-10 19:14 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-10 16:52 [PATCH 0/3] A better way of handling upstream information in git-branch Carlos Martín Nieto 2012-07-10 16:52 ` [PATCH 1/3] branch: introduce --set-upstream-to Carlos Martín Nieto 2012-07-10 17:08 ` Matthieu Moy 2012-07-10 17:26 ` Junio C Hamano 2012-07-10 19:13 ` Jonathan Nieder [this message] 2012-07-10 19:49 ` Junio C Hamano 2012-07-10 20:11 ` Jonathan Nieder 2012-07-10 20:49 ` Junio C Hamano 2012-07-10 21:09 ` Jonathan Nieder 2012-07-10 23:13 ` Junio C Hamano 2012-07-10 23:47 ` Jonathan Nieder 2012-07-11 1:20 ` Junio C Hamano 2012-07-11 1:37 ` Jonathan Nieder 2012-07-12 8:41 ` Miles Bader 2012-07-12 16:58 ` Junio C Hamano 2012-07-10 16:53 ` [PATCH 2/3] branch: suggest how to undo a --set-upstream when given one branch Carlos Martín Nieto 2012-07-10 17:20 ` Matthieu Moy 2012-07-11 13:50 ` Carlos Martín Nieto 2012-07-10 17:40 ` Junio C Hamano 2012-07-11 14:24 ` Carlos Martín Nieto 2012-07-10 19:24 ` Jonathan Nieder 2012-07-10 22:43 ` Junio C Hamano 2012-07-10 23:00 ` Jonathan Nieder 2012-07-11 15:14 ` Carlos Martín Nieto 2012-07-10 16:53 ` [PATCH 3/3] branch: add --unset-upstream option Carlos Martín Nieto 2012-07-10 18:02 ` Junio C Hamano 2012-07-11 14:14 ` Carlos Martín Nieto 2012-07-11 16:53 ` Junio C Hamano 2012-07-12 10:27 ` Carlos Martín Nieto 2012-08-20 13:47 [PATCH 0/3] Improve branch UI for setting upstream information Carlos Martín Nieto 2012-08-20 13:47 ` [PATCH 1/3] branch: introduce --set-upstream-to Carlos Martín Nieto 2012-08-30 17:23 [PATCHv2 0/3] Improve branch UI for setting upstream information Carlos Martín Nieto 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
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=20120710191354.GE8439@burratino \ --to=jrnieder@gmail.com \ --cc=Matthieu.Moy@grenoble-inp.fr \ --cc=cmn@elego.de \ --cc=git@vger.kernel.org \ --cc=gitster@pobox.com \ --subject='Re: [PATCH 1/3] branch: introduce --set-upstream-to' \ /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.