[PATCH][BUG] The 'bzr check' command doesn't check the merged revision

[Goffredo Baroncelli]

On Thursday 08 September 2005 19:56, you (Aaron Bentley) wrote:
> Goffredo Baroncelli wrote:
> > On Wednesday 07 September 2005 21:31, Aaron Bentley wrote:
> 
> >>Checking them is fine, but merged revisions aren't guaranteed to be
> >>present in storage, so you should not treat their absence as an error.
> >
> >
> > How it is possible to merge some revisions without storing these into the repository ?
> 
> When you merge a revision, you implicitly merge its parent revisions,
> too.  So you don't need to have access to the parent revisions.

I don't fully agree. I think that the user should decide what merge. Sometime is more 
useful to merge only the full branch as unique revision, sometime is more useful to 
merge all revisions of a branch.

However should you clarify if now ( 0.7 ) bzr merge only the latest revision or the full
history ? On the basis of my test it seems that every revision is merged.

[...]
> Aaron
Goffredo 

-- 
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack at inwind.it>
Key fingerprint = CE3C 7E01 6782 30A3 5B87  87C0 BB86 505C 6B2A CFF9