Re: [fossil-users] Cannot determine user when using -A
Fossil certainly will spawn external programs if you: 1) start a commit w/o a command-line commit message 2) run a did with an external diff-command configured. , maybe others. On Jun 7, 2014 12:00 PM, Ron Wilson ronw.m...@gmail.com wrote: On Sat, Jun 7, 2014 at 11:52 AM, Stephan Beal sgb...@googlemail.com wrote: On Sat, Jun 7, 2014 at 5:18 PM, Will Parsons varro@nodomain.invalid wrote: Or you should be able to simply set the environment variable: $ USER=philip_bennefall and then you don't need to worry about the -A or --user options. That would work, but note that many programs use $USER to create strings (paths) and such, so reassigning it is generally not a good idea. However... export FOSSIL_USER=philip_bennefall should do the trick without endangering any other apps. Also: env USER= philip_bennefall fossil command options etc Will run fossil will that value of USER but not affect other things (unless fossil invokes them, but fossil doesn't do that) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ 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] Cannot determine user when using -A
On Sun, Jun 8, 2014 at 3:25 PM, B Harder brad.har...@gmail.com wrote: Fossil certainly will spawn external programs if you: 1) start a commit w/o a command-line commit message 2) run a did with an external diff-command configured. , maybe others. 3) A new process is started to handle each incoming HTTP request when you run fossil ui or fossil server. 4) gpg is run in a separate process to sign checkins, if you have checkin signing enabled. 5) ssh is run as a separate process if you push or pull using the ssh: protocol. 6) The fossil all sync command (as well as other subcommands under all) starts a second fossil instance in a separate process for each repository to be synced. -- 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
Re: [fossil-users] Cannot determine user when using -A
On Sun, Jun 8, 2014 at 3:25 PM, B Harder brad.har...@gmail.com wrote: Fossil certainly will spawn external programs if you: 1) start a commit w/o a command-line commit message 2) run a did with an external diff-command configured. I had been thinking about hooks and discussion of multi platform support issues. I had forgotten about invoking an external editor or diff tool. (I had not forgotten about Fossil forking copies of itself. I just wasn't counting those as external tool invocations.) ___ 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] autosync from GUI
On Sat, Jun 7, 2014 at 4:37 PM, Scott Robison sc...@casaderobison.com wrote: On Jun 7, 2014 1:27 PM, Ron Wilson ronw.m...@gmail.com wrote: On Sat, Jun 7, 2014 at 2:23 PM, Stephan Beal sgb...@googlemail.com wrote: For the local UI case, sure, i can see it being useful, but people would also expect it to work remotely, and it often wouldn't. When running the local UI, that is seen as part of the local client, but when accessing a remote server the perception is different. I think it reasonable that the server Fossil not try to autosync to another server Fossil. Please forgive what may be a stupid observation, but if there are users that need ticket or wiki access (workflows that are typically ui only), might not the best approach be to give them appropriate access to the master via http (as someone already says they do indirectly by making that the master copy)? Not stupid. I suspect many Fossil installations do that. The Fossil and SQLite main sites do that. Sometimes, thought, that isn't practical. When those people aren't in the office, its not too hard for them to understand that the syncs don't happen. In the office, however, it is natural for them to expect the syncs are done automatically. ___ 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] autocrlf like in Git?
On Sat, Jun 7, 2014 at 8:37 PM, Nico Williams n...@cryptonector.com wrote: The same is true for git, and Mercurial, and... It doesn't mean it can't be done, just that the VCS has to know how to canonicalize the file's contents, and that is awful. But sometimes someone has no choice. Depends on how you define no choice. I can't speak to git, et al, not turns out one of my coworkers was a student of the creator of RCS, Walter Tichy, and did work on RCS at that time. (Disclaimer: I am NOT advocating building the auto conversion into Fossil, only relaying a story of how one port of RCS acquired the auto conversion. (I really don't think it should be in Fossil or other VCS.)) When he graduated, his first job was at a company that was, at the time, using terminal connected to a VAX running BSD Unix. Then company started getting PCs, which ran MS-DOS back then. At first, they continued to develop on Unix, only pulling down source files when they needed to compile on MS-DOS. Of course, this required runing the files through unix2dos, but this was part of the script that pulled the files from the Unix system. Then another graduate was hired and he brought with him a very early MS-DOS client for Unix file servers. Very soon, management asked if there was a way to run RCS on MS-DOS. My (now) coworker volunteered to port RCS to MS-DOS. Because they were also versioning WordStar and other types of non-text files, his port of RCS did not use MS-DOS's text mode to read/write files, so unix2dos and dos2unix were still required. At first, that continued to be hidden in the makefiles, but then management decided the team should start doing their development on MS-DOS and only push files to the Unix system for compiling. At first, my friend just reworked the makefiles to convert and commit any changed files as part of the build process, thus leaving the source files in CRLF format on the PCs. And created and update script that would automatically update a developer's working spacing from RCS. But soon, people started using RCS directly, like they had on Unix. This created a big mess. Management's response was to move the conversion to the Unix side, leaving the sources in RCS in CRLF format. This worked until older versions was needed. Although the makefiles still had the conversion in them, editing the files became an issue and people was constantly forgetting to use unix2dos. Then management decided the conversion had to be done in RCS. At first, my friend created a .bat file around RCS for the developers, but this had problems, so he finally had to add the conversion to RCS. Actually, it was just the logic to decide when to convert. He doesn't if it was his port to MS-DOS actually made it into the master RCS repo, but whichever one did, it's likely it did arise from a situation like this one, where it was the expedient thing to do. While I suspect Linus and company may not have included the auto conversion in git, later maintainers likely decided it was expedient to do so, whether from their own experience or just bowing to a plentitude of requests from the user community. (Since SVN was intended to replace CVS and CVS evolved out of RCS, I am guessing that SVN inherited auto conversion from RCS.) ___ 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] autocrlf like in Git?
On Sun, Jun 8, 2014 at 7:15 PM, Ron Wilson ronw.m...@gmail.com wrote: On Sat, Jun 7, 2014 at 8:37 PM, Nico Williams n...@cryptonector.com wrote: The same is true for git, and Mercurial, and... It doesn't mean it can't be done, just that the VCS has to know how to canonicalize the file's contents, and that is awful. But sometimes someone has no choice. Depends on how you define no choice. [long] Did you read what I wrote after that? Nico -- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
