SVN for src, status?

[Ian Lance Taylor]

"Joseph S. Myers" <joseph@codesourcery.com> writes:

> Then Git is not yet ready for the src repository, in my view, unless you 
> can make it look to users like they are running a single commit command to 
> the central repository with the details of submodules being hidden in the 
> implementation of that command; commits to both BFD and another directory 
> using BFD are a very common use case for this repository, and version 
> control systems firstly need to make the common cases easy and reduce the 
> risk of user error in the common cases.  Checking out just one component 
> of src (e.g. binutils or GDB, with their overlapping sets of directories 
> and common toplevel), updating such a checkout, and checking in (to the 
> central repository) changes across such a checkout, are likely the most 
> common use cases.

Can GIT support a single commit covering multiple repositories?  If it
can, then we could split libiberty and bfd/opcodes into their own
repositories.  I guess the important question would be whether a push
can succeed or fail atomically across multiple repositories.

Ian