Jay Soffian <jaysoffian@xxxxxxxxx> wrote: > 1. Deprecate --track and --no-track (remove from documentation and > usage). I wonder if anyone ever uses them? I use --no-track quite frequently, and I always find it unfortunate that I have to (sometimes I forget). I need it when I want to create a new local branch off of master, and my local master is not up to date, but I'm too lazy to bring it up to date because I have some other branch checked out currently; so I do $ git fetch $ git checkout -b new_branch origin/master This will by default make origin/master the upstream branch of new_branch, which is never what I want. To avoid the problem, I would have to $ git checkout master $ git pull $ git checkout -b new_branch I guess I would like a config setting of branch.autosetupmerge=onlyifnamematches or some such. I realize this is probably not related to the discussion of whether or how --set-upstream should be fixed; I just wanted to comment on your question. -- Stefan Haller Berlin, Germany http://www.haller-berlin.de/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html