On Tue, Aug 12, 2008 at 07:41:55PM -0300, martin f krafft wrote:
> also sprach Santi Béjar <[EMAIL PROTECTED]> [2008.08.12.1828 -0300]:
> > I don´t know if it fits topgit, but this is what Junio uses:
> > http://article.gmane.org/gmane.comp.version-control.git/24498
> I think this is definitely something TopGit can automate.
This seems to be in principle the same as the tie branches. It might
make sense to have a way to _optionally_ make a tie branch.
How should that work? Maybe there needs to be even an explicit support
for this - should TopGit just check the dependency tree when
sequencing the topic branches and have a step that says:
"I'm going to sequence branch A. If there is branch T that has
only already sequenced branches + branch A as dependencies,
use T's content instead of A."
Would that be satisfactory?
Finding out this information would be very expensive, of course. But for
other reasons, we might want to keep a cache of branch dependencies.
Of course, in the case of
the sequenced branches would still be like
unless you create the T1..T4 branches manually.
Petr "Pasky" Baudis
The next generation of interesting software will be done
on the Macintosh, not the IBM PC. -- Bill Gates
vcs-pkg-discuss mailing list