marrying bundle and directive? (Re: [MERGE] Merge directive format 2, Bundle format 4)
mbp at sourcefrog.net
Mon Jul 2 05:54:23 BST 2007
To step back a bit: there are a few different ways in which we can
emit a file containing version information. It can contain a bundle
of revision information, or a merge directive, or both. But in all
cases it takes a branch as input, and usually another as a
reference/base, and writes out a file.
I think, ideally, we only need one command to do this, with options
controlling just what is sent. Do we agree that there should be only
'bundle' is shorter than 'merge-directive' but neither name is really
great because of contradictions like 'bundle --no-bundle'.
How about a new name like 'emit'? (Most commands are verbs, it might
be good if this was.) That lets us look agresh at what the syntax
More information about the bazaar