Quoting Junio C Hamano <gitster@xxxxxxxxx>: > The only use case I've heard in this thread and nearby is where you are > the one who started the history of the branch, and pushed it into a public > repository as a new branch, making the result _the_ most authoritative > one. After that, everybody else will be able to have a local branch that > tracks the authoritative one with "branch --track frotz origin/frotz", and > you will be the only one left unable to do so because you already have > that frotz branch. > > And for that use case, I find it sensible if we had a way to easily say > "This branch hasn't been tracking anything so far (because it is the > originator of the history), but now it will give up its authority and > start tracking the one it is pushing into", and it would make sense to > somehow link that to the invocation of "git push". > > Side note. I would also accept "It is only one person in the world, > who can edit .git/config and be done with it; why bother complicate > the UI for other people" as a valid argument against it, though ;-). > > In that "my private branch gave autority to the branch at my public > repository" case, it is of course easy to re-clone (or "branch -m" away > and then re-fetch) like everybody else, but then you would lose the reflog > from the time before the branch went public, so it is not a solution but a > poor workaround. I'm sorry, but I don't understand why you want to keep the entries in the reflog that were made before you pushed your branch to make it public in this scenario. Especially because you are relinquishing the authority to the public repository by wishing to be able to "track" it, you can't rewind the branch beyond the point you initially pushed out any more. At that point, wouldn't it make more sense to drop the old reflog data and pretend as if the branch were fetched from the branch from your public repository it now follows, just like everybody else does? -- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/ -- 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
