History Of Ticket 3cce33ff2f0a414dcb35dd6d36f48961797e037e
Not logged in
Ticket change [3e3054184b] (rid 3277) by drh on 2008-07-25 11:54:48:
  1. Appended to comment:

    drh added on 2008-07-25 11:54:48:
    See comment on ticket bd33a464ae: The "branch" command seems to be an abandoned subproject of a developer who has not contributed to fossil lately. I do not know what its purpose is. I am of a mind to delete the command all together. Please take discussion to the mailing list.

  2. Change priority to "Immediate"
  3. Change private_contact to "63f4cb9d6971f7dbdee05412b8546975182b32e4"
  4. Change resolution to "Not_A_Bug"
  5. Change status to "Closed"
  6. Change subsystem to "one"
Ticket change [22d86624b6] (rid 3274) by anonymous on 2008-07-25 04:17:15:
  1. Change comment to "If I perform a <verbatim> fossil help branch </verbatim> Fossil do not mention, that I can pass the option <tt>--nosign</tt>. During creation of the branch, I was asked to pass my private key's passphrase to sign the creation. I did not want to do this and therefore interrupted the branch creation process. I tried the same command line and added a <tt> --nosign</tt> somewhere. This time the creation succeed without asking me for my passphrase. So I conclude that the description of the applicability of said option is lacking. But another three question: why to I have to sign the creation of a branch and not the creation of a tag? And what is the difference between <verbatim> fossil branch new test </verbatim> and <verbatim> fossil tag add branch sym-test </verbatim> And last but not least, what is the idea for a <tt>tag</tt>? I do not seem to be able to </tt>fossil update</tt> to a tag-marked version."
  2. Change foundin to "4b56350ecb"
  3. Change private_contact to "63f4cb9d6971f7dbdee05412b8546975182b32e4"
  4. Change severity to "Important"
  5. Change status to "Open"
  6. Change title to "Help of branch new does not mention option --nosign"
  7. Change type to "Documentation"