Overview
Artifact ID: | a828bbf2baba60a091905f26269f51c7642be1da |
---|---|
Ticket: | e24ec32b1da5f8f5e4abe3b1eed6899f8be6f4cc
privateness not preserved |
User & Date: | anonymous 2011-03-23 20:15:49 |
Changes
- Appended to comment:
<hr /><i>anonymous added on 2011-03-23 20:15:49 UTC:</i><br /> This patch seems to fix the problem with "fossil branch new" from a private checking not preserving said privateness. Also fixes the problem with being prompted for a key even though the clearsign option is defaulted to off. Seems like the logic for cancelling propagating tags between checkin.c db_prepare(&q, "SELECT tagname FROM tagxref, tag" " WHERE tagxref.rid=%d AND tagxref.tagid=tag.tagid" " AND tagtype==2 AND tagname GLOB 'sym-*'" " AND tagname!='sym-'||%Q" " ORDER BY tagname", vid, zBranch); and branch.c db_prepare(&q, "SELECT tagname FROM tagxref, tag" " WHERE tagxref.rid=%d AND tagxref.tagid=tag.tagid" " AND tagtype>0 AND tagname GLOB 'sym-*'" " ORDER BY tagname", rootid); is a bit different. My sql is a bit rusty so i'm not sure if they accomplish the same things just in different manners. Still not sure why "delete from private" and then a fossil rebuild still leaves artifacts in the private table.
- resolution changed to: "Open"