On Wed, Sep 8, 2010 at 1:07 PM, Nolan Darilek <no...@thewordnerd.info>wrote:
> -----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? > Notice that the old commit message (and date/time and user) are not deleted. They are retained and you can see them when you click on the details page for a checkin. The new commit message, etc, are merely shown on the timeline. The ability to check-in and push implies the ability to edit commit messages. It would be silly to do anything otherwise. If you have a clone on your local machine, you can do anything you want to that clone since you own the file. And then if you push, anything you did to your clone gets transferred to the server. So the ability to push implies a lot of power. The philosophy behind Fossil is "low-ceremony". Rather than have lots of fine-grain permissions, let trusted developers do whatever it is they need to do in order to get the job done. Don't let permissions stand in the way. Mischief is prevented by an unforgeable audit trail and the "timeline" that allows administrators to monitor changes to the project easily. > > > 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 > -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
