Re: [fossil-users] RFC regarding short UUID for some command line use.
Thus said Joe Mistachkin on Sat, 07 Mar 2015 22:05:48 -0800: Personally, I agree. I find having the abbreviated UUID displayed in this particular context to be quite disconcerting. What about some of the other command line checkin contexts that were changed in [c62e94f8a3]: $ fossil branch new test trunk New branch: d4d5c24326 ... $ fossil merge --integrate test $ fossil ci -m three Closed: 5703dae21d New_Version: da04545d2a Thanks, Andy -- TAI64 timestamp: 400054fbf1a0 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil 1.31 directory name
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/3/2015 1:59 PM, Andy Goth wrote: On 3/2/2015 12:49 PM, Andy Goth wrote: On 2/24/2015 11:31 AM, Joe Prostko wrote: Yes, I wondered about the directory name not matching the filename, but just modified my Haiku build recipe to account for it. I'll be sure to change the recipe file once the tar.gz with the full path is in place. When I have time, I'll have to do the same for the SlackBuild script. Done. I will post again when my submission is approved. Fossil 1.31 has been published to the SlackBuild website. http://slackbuilds.org/repository/14.1/development/fossil/ - -- Andy Goth | andrew.m.goth/at/gmail/dot/com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJU+479AAoJELtYwrrr47Y4/lYIAJjXOeQnU0Kc5H9Xq3wb6MpV uZJ40Y9cemyCCywa8HUMl5mS9dJZGQkaeqYUmflhnufvdthuK7LesTZO0kS0PBLf nLxEa/3YX5gkCqRtTr0VS/lMmYjfXLw9NMOCqeU+WUlODhjUyS6i3cxL7d7ALDqt 2caAbLE9PWbkVXdZx1vqxUWO+HQWxrEaHMC4vChKPo/TNnrY1y+bjfoZaFV5Gaun EJUAce3RTBHSVdXZ4d1fUkz6OiUQAaUKjZd3DSCq2H3nGepkMYLbhQWqXhD+SYej H9S5Gl6MKHKeGNuhEhPyk43fXtQoIM+QpyFdnQDGKyAWmkLxjtVAyxBc/DtUA6s= =9keh -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
[fossil-users] RFC regarding short UUID for some command line use.
Hello, There have recently been some changes to make short UUIDs more prominent, however, I think that new checkins should still display the full UUID: $ fossil ci -m test New_Version: 36eb94ea54 vs $ fossil ci -m test New_version: 36eb94ea547e5905b41e6b447efbfd1184311b23 I think I still prefer to see the full UUID in this particular context, anyone else have an opinion either way on the matter? For command line use, I think it makes sense to display short UUIDs where terminal line width is perhaps limiting, but this UUID does not run the risk of ever going beyond 80 characters. Thoughts? Andy -- TAI64 timestamp: 400054fbe2e7 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] RFC regarding short UUID for some command line use.
Andy Bradford wrote: There have recently been some changes to make short UUIDs more prominent, however, I think that new checkins should still display the full UUID: Personally, I agree. I find having the abbreviated UUID displayed in this particular context to be quite disconcerting. -- Joe Mistachkin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
