From: lm at mcvoy.com (Larry McVoy) Subject: [COFF] [TUHS] Algol 68 and Unix (was cron and at ...) Date: Fri, 18 Dec 2020 11:24:07 -0800 Message-ID: <20201218192407.GC849@mcvoy.com> (raw) In-Reply-To: <X9zp5pKz9cKQrc64@mit.edu> On Fri, Dec 18, 2020 at 12:41:58PM -0500, Theodore Y. Ts'o wrote: > Code archeology > is *definitely* a powerful tool, but this relies on the source control > metadata is sufficiently rich; in some cases, having links to bug > trackers or mailing list discussions are super-useful. > > - Ted Believe it or not, this is one of my major complaints about Git, it only has commit comments, there are no per file comments (because there is no per file meta data other than contents, type, and permissions). BitKeeper has full per file meta data including comments, user who made the change, etc. Which means you can have commits that have more than one author. The GUI tool we built for checkins had 3 panes: list of files that are changed -------------- space for comments ------------- diffs for current file The ChangeSet file, which is just another version controlled file that is the manifest for the repository, its graph is the same graph as Git has, is always the last file of the list of files, but here is the trick: the diffs for the ChangeSet file were all the comments you just typed in. So what do people do? On the files, they tended to say what they did to that file, some bread crumbs specific to that file. On the ChangeSet file, seeing all those comments, they tended "up level" their comments and provide more of a "what" than a "how". Intel looked at the quality of the checkin comments done at the command line vs those done with the GUI tool and mandated the use of GUI tool, the comments were _that_ much more useful.
prev parent reply other threads:[~2020-12-18 19:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CAKH6PiVLgdPVEGvGfyVAwNMz66=0huVyvRY90E+PduwG4ssVRQ@mail.gmail.com> [not found] ` <0EA02917-243E-4612-9F7E-D370EE0A7C2E@ronnatalie.com> [not found] ` <20201217143558.GD13268@mcvoy.com> 2020-12-17 15:22 ` clemc 2020-12-17 15:50 ` [COFF] [SPAM] " lm 2020-12-17 17:57 ` imp 2020-12-17 18:00 ` lm 2020-12-17 18:30 ` [COFF] " 2020-12-17 21:10 ` [COFF] [SPAM] " clemc 2020-12-18 14:43 ` lm 2020-12-18 15:46 ` clemc 2020-12-18 17:41 ` tytso 2020-12-18 19:24 ` lm [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20201218192407.GC849@mcvoy.com \ --to= \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Computer Old Farts Forum This inbox may be cloned and mirrored by anyone: git clone --mirror https://inbox.vuxu.org/coff # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 coff coff/ https://inbox.vuxu.org/coff \ firstname.lastname@example.org public-inbox-index coff Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.vuxu.org/vuxu.archive.coff AGPL code for this site: git clone https://public-inbox.org/public-inbox.git