-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Neat, thanks for the explanation.
I like that I can edit previous commit messages, but that worries me a bit as well. Who can edit a given commit message? I don't see it as a separate permission. Does it come with commit access? On 09/08/2010 11:46 AM, Wes Freeman wrote: > For 1. Just put [10-digit hex ticket id] in square brackets in the commit > comment. Something like: > "Fixed flashing screen when first opening the page. Reported in ticket > [ff6ba964e2]." > > It will automatically make a link to the ticket in the timeline, and the > check-in will show up in the related check-ins for that ticket. > > You can go back and edit check-in (commit) comments if you want to add > tickets after the fact. Open the check-in and click "edit" under "other > links". > > Wes > > > On Wed, Sep 8, 2010 at 12:30 PM, Nolan Darilek <no...@thewordnerd.info>wrote: > >> >> OK, apologies if this is documented somewhere, but finding things in the >> docs is more a process of digging and discovery than of reading straight >> through--perhaps appropriate for a project named Fossil. :) But: >> >> 1. How does one associate commits with tickets? I've looked through the >> ticket edit screen and don't see a way. >> >> > > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEUEARECAAYFAkyHwrQACgkQIaMjFWMehWLD2gCfQMezR/LrXbyq5/HNnwzXH7DG AdgAljz0XjYPBlthesoLBRK3MozNbms= =WT5p -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
