gapon wrote: > hi all, > first of all i don't know if there's a bugzilla or something similar > for git - i have found just this email (on http://git.or.cz/ webpage). There isn't any bug tracker for git. Use git mailing list for bug reports and feature requests. > i have discovered "weird" behaviour of git in this scenario*: > - user A is working in repo A > - user B clones repo A > - user B makes some changes, commits, pushes Do not push into checked out branch! > - user A makes some changes, git status (no info about new commit > in his repo from user B but it's probably ok i'd say - but some > of my files are marked as changed and already added to index > but i haven't changed them - that's confusing, isn't it?) > - user A can commit his changes => shouldn't be there any > info/message/warning displayed? it would be helpful to have > here some info about "foreign commit" in the repo or something > like this Perhaps there should. There was some idea and even preliminary implementation of BASE check, but IIRC it was deemed too complicated, and encouraging wrong workflow. Besides, even with the check, pushing into checked out branch can quite easily lead either to loosing (or at least vanishing) some history, or problems with pushing. > * yes, i know that this scenario is "incorrect" but... it's possible and > therefore i think it should be somehow handled - i tried a similar one > with hg and bzr and i like their behaviour more IIRC we strongly discourage in documentation to push into checked out branch. Either use bare repository for communication (it allows for example for got for "ideal patch series" by rewriting history _before publishing (pushing)_ and for communication with more than one chosen developer), or push into _remotes_, not into heads. -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - 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
