Jens-Heiner Rechtien wrote:
Hi Jan,
Jan Holesovsky wrote:
Hi Bernd,
On Friday 31 July 2009, Bernd Eilers wrote:
Everyone using a mercurial based CWS MUST enter the new milestone in
EIS
manually after rebasing the CWS to a new milestone using mercurial
commandline or gui tools.
Cannot this be automated?
With git, all you'd need is to have a post-update hook on the server
that does 'git describe' (finds the most recent tag that is reachable
from a commit) on the CWS, and just gives the tag to the EIS. I
suppose the same must be achievable with Mercurial, right?
Yes, something like that is possible with hg. But it's somewhat wrong
also because in most cases it's more relevant what's in your local
working repository and that might be much more current than what you
have in the outgoing rep.
So the whole notion of the "current milestone" is somewhat unclear in
a DSCM scenario.
Haven't thought finally about it. There will be at least a command
line method to update the milestone.
what about this: tho code basis itself knows about it's milestone, it's
in solenv/inc/minor.mk, so EIS should be able to grab that information
from the hg repository directly.
Martin
Regards,
Heiner
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
