Fossil

In function cgi_set_cookie the zDate was allocated via usage of cgi_rfc822_datestamp. But as it was appended to the blob extraHeader via the format specifier %z the memory was free'd by blob_appendf. As cgi_rfc822_datestamp might return both a dynamic allocated empty string as well as a dynamic allocated string containing the time stamp, blob_appendf should not try to free the zDate. So now the format specifier is changed to %s to let us decide, if we want to free the memory or not. ... (check-in: aeeba751 user: cle tags: trunk)

That logic seem wrong. As at all other cases, first the ecommend was fetched and only when that failed, the original comment was taken, I corrected the three places in code accordingly. ... (check-in: 589687d7 user: cle tags: trunk)

  417dd898ab0640f2472ebd248ac80e80f0ec6972.zip

  fossil-417dd898ab.zip

As the /zip page do not expose anything, a spider should have a hard time to crawl thru the project using this URL. So IMO it does not open a break-in hole for spiders. ... (check-in: fa6e9930 user: cle tags: trunk)

• Rename subcommand tag delete to tag cancel.

• New branching behavior. Now if subcommand tag branch is used, a new copy of manifest UUID with the same parent will be created, thereby creating a fork. A propagating symbolic tag with TAGNAME is assigned to the UUID of the new copy. Furthermore all other propagating symbolic tags that the fork did inherited by the original manifest, are cancelled.
  
  However, if the option --raw was given, the old tag branch behavior is used. That means, no creation of a fork by copying the manifest UUID, no cancelling of inherited propagating symbolic tags. The tag will be applied to the given UUID directly.
  
  For instance

          fossil tag branch fix-12345 cfcfcfee
          fossil tag branch --raw bgcolor fix-12345 yellow
        

  will create a fork by copiying manifest cfcfcfee, apply a tag fix-12345 that will propagate to its children and set the propagating property bgcolor to yellow.

1. All subcommands of command tag prepends a prefix sym- infront of every tag name passed to them. Tags beginning with sym- are special in Fossil as they might serve as replacement of a UUID they are attached to.
   
   Further, tag list will only list all tags beginning with sym- but with that prefix removed during display as default.
   
   All subcommands can get passed an option --raw, that prevent the prepending of the prefix sym- in front of the tag name. tag list will report all tags without removing any prefix if called with option --raw.

2. If a command takes a tag name that may be confused with a UUID, the command did interpret that parameter as a UUID instead as a tag name. Such tags might now be prefixed with a tag: to enforce the command to take them as tag name instead of a UUID. For example:

           fossil tag add abcde $uuid
           :
           fossil update tag:abcde
         

   without the prefix tag: fossil would try to update to a UUID beginning with abcde. If no such UUID was found, fossil will complain and exit.