Mats Lidell writes:
>>>>> Stephen J Turnbull <stephen(a)xemacs.org>
writes:
> If at each release we try to include only commits since the last
> release date, we lose all the commits on branches merged more
> recently that were committed before that date.
I can't recreate this problem but probably I haven't understood the
use case. Could you provide a simple scenario, use case, that
illustrates this?
Consider the following sequence:
Time Mainline Branch
0 A --------- A Create branch at revision A
| |
1 | B Revision adding feature B
| |
... [many commits on mainline]
| |
102 C | Release version C 3 months later
| |
103 | D Revision adding feature D
| /
104 E --------+ Revision merging branch to mainline
Now "hg log --date 102" will list C, D, and E, but not B. This is
bad, because the code for B is not in C, but is in E, and therefore
relevant to debugging E.
That's what worries me, anyway. I think I already mentioned that I
know how to script this in git, but I think in Mercurial it would need
to be a Python plugin.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta