Re: [fossil-users] [Nmh-workers] Merging Source Files with git. (fwd)
On 11/14/17, Warren Young wrote: > > If anyone wants it, they can consider it to be under the SIMH license: > Can I make it would of the built-in skin options in Fossil? -- 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] [Nmh-workers] Merging Source Files with git. (fwd)
On Nov 14, 2017, at 2:42 PM, Stephan Beal wrote: > > On Tue, Nov 14, 2017 at 4:26 PM, Warren Young wrote: > https://tangentsoft.com/pidp8i/finfo?name=libexec/mkos8 > > Don't take this the wrong way, but that is a mighty fine skin you have, sir. Thank you. It’s largely just a recoloring of the default skin plus some whitespace and border effects. It is meant to evoke amber video terminals and early PDP-8 computers. I call the skin “Amber VT”. If anyone wants it, they can consider it to be under the SIMH license: https://tangentsoft.com/pidp8i/doc/trunk/SIMH-LICENSE.md I’d like to see my new /bugs and /features links become more popular, and I think the change to the Wiki button’s target makes more sense as a default. ___ 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] [Nmh-workers] Merging Source Files with git. (fwd)
On Tue, Nov 14, 2017 at 4:26 PM, Warren Young wrote: > https://tangentsoft.com/pidp8i/finfo?name=libexec/mkos8 Don't take this the wrong way, but that is a mighty fine skin you have, sir. -- - stephan beal http://wanderinghorse.net/home/stephan/ "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf ___ 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] [Nmh-workers] Merging Source Files with git. (fwd)
On Nov 14, 2017, at 8:21 AM, Warren Young wrote: > > What Fossil could backtrace automatically, and still doesn’t, are renames. > Change a file’s name and the “finfo” terminates at the rename point. To clarify: I realize that Fossil *remembers* each rename. What I’m wishing for is that /finfo and such would trace back through each rename automatically. Here’s a motivating example: https://tangentsoft.com/pidp8i/finfo?name=libexec/mkos8 That file changed names 5 times early in its life before settling down. I think the full history should be shown on the first page, rather than require that the user scroll to the oldest checkin on each page and click on the “Renamed from [f00]” link. ___ 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] [Nmh-workers] Merging Source Files with git. (fwd)
On Nov 11, 2017, at 5:14 AM, Richard Hipp wrote: > > There is no way to track file merges in Fossil. Nor is there a way to > track splits - when a single source code file is split into multiple > smaller files because the original became too large. Whenever I’ve had to do that, I add a line explaining the file’s provenance to the module’s header comment: Merged from foo.c and bar.c on 2017.11.14 by Warren Young or Extracted from foo.c on 2017.11.14 by Warren Young Between that and the checkin comments near that date, I can backtrace merges and splits manually. What Fossil could backtrace automatically, and still doesn’t, are renames. Change a file’s name and the “finfo” terminates at the rename point. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
