Update: Re: bzr 0.6 commit problem: parent_id {blah} not in inventory

[Michael Ellerman]

On Thu, 3 Nov 2005 20:24, Andrew S. Townley wrote:
> ...
> Sorry, that got a bit long, but the sort version is that I believe bzr
> (or any other VCS) should always allow atomic commits at the single file
> level, regardless of what happened in the tree.  This isn't the first
> time I've hit a similar issue in the last few days, but I didn't have as
> many changes pending, so it wasn't that big of deal.  Yesterday, I had
> refactored some bits, and added some significant new bits, all of which
> logically hung together as a single unit of functionality.  That still
> doesn't mean that I believe they should have all had a blanket log
> message.

That's one school of thought. The other is that you should never check in 
something that doesn't build and or work. "Don't break the build!"

If you think about it, partial commits allow you to create revisions in 
history that never actually existed in your working tree, which means you 
never built or tested them. 

So I agree that it's important not to have a 2K diff of 100 files that says 
"Updated stuff", I also think it's dangerous to check in revisions that you 
haven't built, no matter how careful you are you'll get it wrong one day.

cheers

-- 
Michael Ellerman
IBM OzLabs

email: michael:ellerman.id.au
inmsg: mpe:jabber.org
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051103/c425b409/attachment.pgp