Java Virtal Machine.net
    :Microsoft VM: :Sun JVM: :Other JVMs: :Download: :Tech FAQ: :Forum: :Java Menus: :DHTML Menu:

    [ News ] rss

    March 14, 2010

    Stephen Colebourne: Java language design by use case. In a blog in 2006 Neal Gafter wrote about how language design was fundamentally different to API design and how use cases were a bad approach to language design. This blog questions some of those conclusions in the context of the Java language.

    More »

    March 13, 2010

    FindBugz Community Review. I am very fond of FindBugz (indeed it has found its way into the QA process of most projects I work on....). When visiting the site to check Eclispe 3.5.2 compatibility I found they were working on a new tool. Indeed a very interesting tool. Looks li...

    More »

    March/2010
    SunMonTueWedThuFriSat
     1 2 3 456
    789 1011 12 13
    14 15 1617181920
    21222324252627
    28293031   

    [ Archives News
    for 'Developers' ]
    home > news > developers > mercurial tip: checking in regularly with uncommitted changes in your clone

    Mercurial Tip: Checking in regularly with uncommitted changes in your clone

    NetBeans, like OpenJDK and OpenSolaris, uses the Mercurial distributed version control system. I'm a big fan of of distributed version control. However, one thing that drives me nuts is this error message: % hg merge abort: outstanding uncommitted changes This isn't just going to be a rant - I've finally found a solution which is working extremely well for me. I've suggested it to some other developers who have also reported that it works well for them, so I thought I would share it with you. The reason I run into this all the time is my preferred style of work: I like to work on many things simultaneously. If while working on something, I come across a bug and I spot the problem, I just fix it right there and add a test for it. When I get ideas, I might go and put @todo tasks for myself, or leave editorial comments in various source files. I might also work on a couple of larger tasks simultaneously. Yes, I know the preferred Mercurial idiom for this is to have multiple clones, one for each task - but that isn't my preferred way of doing it. Each NetBeans clone is huge and takes a while to both clone and build - and I would have to switch my IDE editing context between these large source trees all the time. I like to check things in in logical chunks with a message that pertains to that particular change. This means I often check in a subset of the edited files in the tree. I like to check in code regularly ra...


    Date: October, 31 2008
    Url: http://blogs.sun.com/tor/entry/mercurial_tip_checking_in_regularly


    Others News

    Leave a Reply

    Name (required)
    Mail (will not be published) (required)
    Website
    You don't see letters?

    Enter the code shown above (required)


    Related
    ©2002-2008Java-Virtual-Machine.net