lkml.org 
[lkml]   [2002]   [Feb]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Bitkeeper change granularity (was Re: A modest proposal -- We need a patch penguin)
    Rob Landley <landley@trommello.org> wrote:
    >
    > The problem is, if they use bitkeeper (with a temporary respository), all
    > these temporary commits (debugging tries saved in case they want to roll back
    > during development) get propagated into the main repository when they do a
    > merge. They can't tell it "done, okay, squash this into one atomic change to
    > check in somewhere else, with the whole change history as maybe one comment".

    Something like:

    bk start-temporary-fork
    [hack hack hack]
    bk commit
    [hack hack hack]
    bk revert
    [hack hack hack]
    bk commit
    [hack hack hack]
    bk commit
    bk fold-back-into-main-tree-as-one-atomic-update

    ?

    Charles
    --
    -----------------------------------------------------------------------
    Charles Cazabon <linux@discworld.dyndns.org>
    GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
    -----------------------------------------------------------------------
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:23    [W:4.185 / U:0.196 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site