How to see which user has checked out source

Martin Pool mbp at canonical.com
Thu Jul 20 02:25:03 BST 2006


On 19 Jul 2006, John Arbash Meinel <john at arbash-meinel.com> wrote:

> > I have various source repositories created and programmers then checkout
> > into their local directories, do the changes and then commit and I then
> > update and commit on the source repository.  In other words I am using a
> > decentralised with shared mainline workflow.
> 
> So do you have a central set of branches, one for each developer, and
> then you personally merge things into the mainline?
> 
> The biggest thing is knowing whether the changes the developers make are
> showing up somewhere other than on their local machine. (You used the
> term checkout, so it sounds like it is).

To expand on John's answer a bit: if you want to keep track of what your
developers are doing, then it's probably a good idea to require them to
keep a copy of all their branches on a central machine.  (Other people
can look at them, they're not lost if a laptop is stolen or a disk dies,
etc...)  With bzr you can do this by either having just a checkout on
the developer's personal machine, or by regularly pushing up.

But if people aren't coordinating their work a social fix is probably
best - for example, before starting something new, send mail to a
developer list describing what they're going to do, and in which branch
they're going to do it.
-- 
Martin




More information about the bazaar mailing list