hi,<br><br>some notes from my experience<br><br><div><span class="gmail_quote">On 4/23/07, <b class="gmail_sendername">Rohit Rai</b> <<a href="mailto:rohitbrai@gmail.com">rohitbrai@gmail.com</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span class="q"></span><div>How does Bazaar compare to SVN or the commercial SCMs like Perforce, Clearcase on this one? Means how weak/stromng it is in their comparison while dealing with non plaintext data. Specially, XML.
</div></div></blockquote><div><br>IMHO bzr is handling it pretty well, theres possibly two main problems with non-plaintext files:<br>1) the diffs doesn't mean much, (eg. with doc files you have to use the old or the new version),
<br> but with xml you have some sort of a chance to fix conflicts.<br>2) we don't handle very big files that well yet (eg. 1GB files)<br></div><br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span class="q"></span><span class="q"></span><div>Will the record log that developer XYZ had made the particular change be maintained when the PQM commits the paatch to the main repository, or everything on the main repository will show up as a commit/development done by the PQM. That is important with statistical point of view in a software
company.At one location I have seen similar flow using SVN, but finally in the log we notice that all the commits are made by PQM, and the name of the original developer are lost.</div></div></blockquote><div><br>Bazaar handles this beautifully!!
<br>because we use bundles (AKA MergeDirective) to submit patches, <br>which contains all of the meta-information of a<br>diff, rather than just containing the patch information.<br><br>There is unfortunately not as much documentation about this on the wiki as I would have hoped for.
<br><a href="http://bazaar-vcs.org/Specs/MergeDirective">http://bazaar-vcs.org/Specs/MergeDirective</a></div><div><a href="http://bazaar-vcs.org/Workflows">http://bazaar-vcs.org/Workflows</a><br>also see 'bzr help bundle' and 'bzr help merge'
<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><ol><li>First problem is the commit time of the patch may be prolonged at reviewer of gateway post
</li><li>Will all the histroy of modifications by the developer and his log comments be maintained?</li><li>There are a few interesting use cases when, Developer writes a patch and sends it to the reviewer and coninues writing his next patch. What code base should he write this patch against. The global base or his modified base?
<ol>
<li>Suppose he writes it against the global code base, in the meanwhile, the reviewer and gatekeeper approve the patch1 and it makes to the global repos. Does the next patch that the developer sends apply to the global repos when it is sent?
</li><li>Suppose he works against his local copy and generates patch2, in the meanwhile his patch1 is rejected and returned to him, he has to revert that patch and keep patch2, how does that work? Does the patch2 apply to the global codebase when approved?
</li><li>How important is the sequence of patches?</li></ol></li></ol></blockquote><div> </div></div>because of bundles, these aren't a problem <br><br>regards<br>marius<br><br><br>-- <br>I don't trust a Revision Control System with less than 6400 unit tests.