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
Hi Jan,
Jan Holesovsky wrote:
Hi Heiner,
On Wednesday 26 August 2009, Jens-Heiner Rechtien 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?
W
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-
Hi there!
Philipp Lohmann wrote:
Cool, this simplifies hg CWS handling a lot. However may I suggest
putting in the current milestone into the edit field on the page where
you edit the CWS properties ?
Well yes this was a bug which has been fixed now!
Kind regards, pl
Regards,
Bernd E
Cool, this simplifies hg CWS handling a lot. However may I suggest
putting in the current milestone into the edit field on the page where
you edit the CWS properties ?
Kind regards, pl
Bernd Eilers wrote:
know about EIS at all. Thus in order to not break processes which depend
on the correct
Hi there!
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.
For SVN and CVS Childworkspaces the "cws rebase" Kommand stored the
information about a new milestone in EIS. Mercu
