Add a few observations to the merge-tracking requirements.
commit5eb55762c8fdf8e8bb0b267949728df159acdc33
authorglasser <glasser@612f8ebc-c883-4be0-9ee0-a4e9ef946e3a>
Tue, 4 Dec 2007 23:04:07 +0000 (4 23:04 +0000)
committerglasser <glasser@612f8ebc-c883-4be0-9ee0-a4e9ef946e3a>
Tue, 4 Dec 2007 23:04:07 +0000 (4 23:04 +0000)
tree83a9e0f4ed63eaea5b3cb1d80a1138cb584f7ef8
parent99948b893a52b67ddac91b046908159734428345
Add a few observations to the merge-tracking requirements.

* www/merge-tracking/requirements.html
  (repeated-merge): Note that svk doesn't really support
   cherry-picking in sense compatible with repeated merge.
  (cherry-picking): Note that cherry-picking in multiple directions is
   difficult.

git-svn-id: http://svn.collab.net/repos/svn/trunk@28249 612f8ebc-c883-4be0-9ee0-a4e9ef946e3a
www/merge-tracking/requirements.html