Richard Lowe wrote:
> Vladimir Marek <Vladimir.Marek at Sun.COM> writes:
>>> - What else? Please send me questions/issues you want to discuss
>> Documentation. Best practices (should I create branch in workspace or
>> rather create new clone; and why ?). What to do if Mercurial screws
>> repository (happens to me ~ once a week). Differences between mercurial
>> and wx/teamware.
>
> I think these are largely separate from the gate/gk issues.
hmm, don't think I agree. Documentation is certainly one of
my big issues before the switch, particularly since as the
sfw gatekeeper I will likely be the one getting all the questions,
but without any answers.
I know of the hg book but haven't read it yet so I don't know
if it is all that we need, but it's probably too much to tell
someone to read who just wants to know how to bringover like
they used to, so I'd indeed like a teamware->hg
cheat sheet (which would hopefully include info about wx
operations you're used to and how they relate now in hg). I
think I've seen one of those floating around so that might
be done (but I don't know, and it was a long time ago).
As to how to repair a repository.. we'll, I'm not sure if we
need that though I'm alarmed if it's happening once a week.
I know the ON teamware->bridge can have its bi-weekly troubles but
I hadn't seen hg corruption there (well, unless I interrupt
an 'hg pull -u -v' but it's not corrupted just not updated
completely).
Mike
