
Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [tlug] Chrome ate my profile
- Date: Tue, 10 Apr 2018 09:46:32 +0900
- From: Curt Sampson <cjs@example.com>
- Subject: Re: [tlug] Chrome ate my profile
- References: <23205.16405.527594.15212@turnbull.sk.tsukuba.ac.jp> <20180311165823.GA1669@wismut> <ba01bbb1-32d0-7b3c-b3b3-b4d0ed4c6d9a@dcook.org> <23210.6885.521848.717987@turnbull.sk.tsukuba.ac.jp> <20180315104007.26t7l46c6hqfrdxm@iambic.cynic.net> <23211.61661.137765.239583@turnbull.sk.tsukuba.ac.jp> <20180318014444.i5wg6pbq6b4fqwsm@idyllic.cynic.net> <23215.28961.204351.418662@turnbull.sk.tsukuba.ac.jp> <20180319093203.njtzgav5kc2h3hdr@iambic.cynic.net> <23238.64826.608048.103244@turnbull.sk.tsukuba.ac.jp>
- User-agent: NeoMutt/20170113 (1.7.2)
On 2018-04-06 13:53 +0900 (Fri), Stephen J. Turnbull wrote:
> They *are* commits. They're just on a branch that is used only by
> this function, which function is invoked by XEmacs automatically every
> time I save.
I seem to hear you saying you generate a new commit every time you
save. I have no idea how that could work. It's not at all like my
workflow.
I usually save every few to few dozen seconds[1], but commit only
every few mintues to few tens of minutes. After an hour or two working
I'm likely to have a half dozen to dozen commits to coalesece into
1-3, and sorting them into bugfixes, refactorings and new work is easy
since they all have commit messages, even if just at the level of what
I produce in ten seconds while distracted ("Maybe fixed that other
thing that Joe said").
Having a hundred commits with no messages to sort through would be a
nightmare for me. But I'm probably missing something here.
[1]: These days it's often to trigger a test run, though there's also
a hold-over reflex from an ancient unreliable VAX.
cjs
--
Curt J. Sampson <cjs@example.com> +81 90 7737 2974
To iterate is human, to recurse divine.
- L Peter Deutsch
Home |
Main Index |
Thread Index