On Mon, Jul 22, 2002 at 08:20:31AM -0700, Tom Rini wrote:
> Possibly, once bitkeeper allowes ChangeSets to only depend on what they
> actually need, not every previous ChangeSet in the repository. IIRC,
> this was one of the things Linus asked for, so hopefully it will happen.
While that would be great.
With all due respect to Larry and the bk team, I think you'll
find determining 'needed changesets' in this case is a _hard_ problem.
How is bk supposed to find that a change depends on a previously
redefined api declared in a set of files othwerwise untouched by the
changeset being exported.
Now , bk could make this a little easier by allowing changesets to
be exported without any dependencies (ala GNU-patch export - but
with metadata for commit messages).
The developer can then use a 'bk undo' to remove the unnessary changeset
for his patch , reapply keeping the commit metadata, test and now
re-export a full bk patch with minimal dependencies.
Unfortuantely I know know way of currently instructing bk to
do this dependency-less export.
-- TTFN Roger. Master of Peng Shui. (Ancient oriental art of Penguin Arranging) GPG Key FPR: CFF1 F383 F854 4E6A 918D 5CFF A90D E73B 88DE 0B3E
This archive was generated by hypermail 2b29 : Tue Jul 23 2002 - 22:00:40 EST