Matthieu Moy wrote: > Then, one other difference is in the UI. bzr shows you commits in a > kind of hierarchical maner, like (fictive example, that's not the real > exact format). > > $ bzr log > commiter: upstream@xxxxxxxxxxxxxx > message: > merged the work on a feature > ------ > commiter: contributor@xxxxxxxx > message: > prepared for feature X > ------ > commiter: contributor@xxxxxxxx > message: > implemented feature X > ------ > commiter: contributor@xxxxxxxx > message: > added testcase for feature X > ------ > commiter: upstream@xxxxxxxxxxxxxx > message: > something else > > No big difference in the model either, but it probably reveals a > different vision of what "history" means. We have in GIT git-show-branch command for that (although it has quite strange UI, and shows only title of commit), we can do "git log | git name-rev --stdin", or better use graphical history viewers like gitk (Tcl/Tk) or qgit (Qt). Graphical history viewers are a must with more complicated history. Bazaar-NG has bzr-gtk. -- 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