hgext3rd/topic/__init__.py
changeset 2012 dc34d5317001
parent 2011 9c7665e3107b
child 2288 b6ea9049693d
equal deleted inserted replaced
2011:9c7665e3107b 2012:dc34d5317001
    25 'hg topics --verbose' will list various information related to each topic.
    25 'hg topics --verbose' will list various information related to each topic.
    26 
    26 
    27 The 'stack' will show you in formation about the stack of commit belonging to
    27 The 'stack' will show you in formation about the stack of commit belonging to
    28 your current topic.
    28 your current topic.
    29 
    29 
    30 In addition, topic is offering your aliases reference to changeset in your
    30 Topic is offering you aliases reference to changeset in your current topic
    31 current topic stack as 't#'. For example, 't1' refers to the root of your
    31 stack as 't#'. For example, 't1' refers to the root of your stack, 't2' to the
    32 stack, 't2' to the second commits, etc. The 'hg stack' command show these
    32 second commits, etc. The 'hg stack' command show these number.
    33 number.
    33 
    34 
    34 Push behavior will change a bit with topic. When pushing to a publishing
    35 Finally, the 'evolve' extension takes 'topic' into account. 'hg evolve --all'
    35 repository the changesets will turn public and the topic data on them will fade
       
    36 away. The logic regarding pushing new heads will behave has before, ignore any
       
    37 topic related data. When pushing to a non-publishing repository (supporting
       
    38 topic), the head checking will be done taking topic data into account.
       
    39 Push will complain about multiple heads on a branch if you push multiple heads
       
    40 with no topic information on them (or multiple public heads). But pushing a new
       
    41 topic will not requires any specific flag. However, pushing multiple heads on a
       
    42 topic will be met with the usual warning.
       
    43 
       
    44 The 'evolve' extension takes 'topic' into account. 'hg evolve --all'
    36 will evolve all changesets in the active topic. In addition, by default. 'hg
    45 will evolve all changesets in the active topic. In addition, by default. 'hg
    37 next' and 'hg prev' will stick to the current topic.
    46 next' and 'hg prev' will stick to the current topic.
    38 
    47 
    39 Be aware that this extension is still an experiment, commands and other features
    48 Be aware that this extension is still an experiment, commands and other features
    40 are likely to be change/adjusted/dropped over time as we refine the concept.
    49 are likely to be change/adjusted/dropped over time as we refine the concept.