Adapting workflow to a DVCS from a CVCS
dhruva
dhruvakm at gmail.com
Fri Oct 24 05:00:40 UTC 2008
Hi,
On Fri, Oct 24, 2008 at 9:13 AM, Doug Simon <Doug.Simon at sun.com> wrote:
> maturing quickly. However, there is one part of the workflow that we
> were used to with the old system that just doesn't appear to have an
> analog in Mercurial. With the previous system, each developer had their
> own CVS repository and it was basically treated as a
> smart FTP system. That is, I could work all day on my machine at work
> and then we leaving for home, check all the changes in, and pull them
> out on my machine at home by doing a CVS update. The main point is
> that I had no need to be concerned about checking broken code as the
> checkin was simply for the purpose of moving my current workspace to
> home.
>
> With Mercurial, I'm struggling to see how I can replicate this. AFAIK,
> all inter-repository Mercurial commands operate at the granularity of
> changesets. However, I'm still a little daunted by how permanent
> Mercurial
> changesets are. I certainly don't want to be creating changesets for
> incomplete work.
You could use MQ (mercurial queue) extension to manage tracked
versions of patches. You could use rebase to merge multiple changes to
fewer changesets.
-dhruva
--
Contents reflect my personal views only!
More information about the Mercurial
mailing list