"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
Thanks for the reply!
mike.kupfer(a)xemacs.org writes:
> >>>>> "ST" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
> ST> What happens if you, oh, add a driver to the kernel? Does that
> ST> driver's early history just get summarized as one big patch to the
> ST> kernel?
>
> Yes. Any history (for that driver) prior to the initial integration is
> dropped. It works out reasonably well in practice (at least for us).
You probably have documentation standards that are generally followed,
though. I don't think I'd want to try it in a non-commercial project.
I've used ancient history and branch history on many occasions.
With Mercurial, Mercurial Queues is one way around it---that's how
develop more complex, multi-changeset changes. I personally don't mind
the "merge artifacts". I tend to agree with John Goerzen's take on the
subject:
http://changelog.complete.org/posts/586-Rebase-Considered-Harmful.html
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta