On Thu, Apr 11, 2013 at 03:41:33AM +0530, Ramkumar Ramachandra wrote: > Jeff King wrote: > > It's not that it's not potentially useful. It's that it may be > > surprising and annoying to users who did not want that. > > Besides, I'm not able to imagine one scenario where this is the wrong > or annoying thing to do. Can you provide an example?
To flesh out my earlier example: $ git clone https://github.com/upstream/project.git $ cd project $ hack hack hack; commit commit commit $ git tag -m 'something of note' my-tag $ git remote add me https://github.com/me/project.git $ git config branch.master.remote me $ git tag -m 'something of note' $ git push master my-tag My intent there is publish both master and mytag, but my-tag goes to origin. It's obvious if you think carefully about (and know) the rules, and it's user error. But what fault do we take for designing a feature that causes confusion? Maybe I am the only one who might make that mistake, and it is a non-issue. But I would be much happier if git said "hey, are you sure you wanted to push to two different remotes?". At least by default. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
