From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Greg Minshall <minshall@umich.edu>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: literate programming, development log -- ideas? (ominbus reply)
Date: Wed, 09 Jun 2021 09:57:12 +0100 [thread overview]
Message-ID: <87sg1rv2jb.fsf@ucl.ac.uk> (raw)
In-Reply-To: <643664.1623172504@apollo2.minshall.org> (Greg Minshall's message of "Tue, 08 Jun 2021 20:15:04 +0300")
On Tuesday, 8 Jun 2021 at 20:15, Greg Minshall wrote:
> Eric, when you use something RCS-like as your version control system, i
> assume that makes grepping to find some old note easy enough. but,
> these days i tend to use git. when (assuming) you use git, do you have
> some easy way to say "well, i had this code that looked sort of like
> this... where was it?"? (sorry, that's really a git question, but ...)
Yes, for SRC (RCS-like), it's straightforward to go into the ,v file and
search. For git, I try to make sure the commit message is as
informative as necessary and then search on the log. The alternative is
git-timemachine which allows me to go back and forward in time looking
at the buffer.
Having said this, I don't often find myself looking for anything in the
history. For major alternatives that might come up during the project,
I use branches. But only with git as I have never figured out how to
get a branch set up in src.
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-549-ga0a87d
next prev parent reply other threads:[~2021-06-09 9:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 11:43 literate programming, development log -- ideas? Greg Minshall
2021-06-07 12:00 ` Juan Manuel Macías
2021-06-08 17:15 ` literate programming, development log -- ideas? (ominbus reply) Greg Minshall
2021-06-08 17:21 ` Samuel Banya
2021-06-09 8:59 ` Eric S Fraga
2021-06-09 22:21 ` Dr. Arne Babenhauserheide
2021-06-10 22:07 ` Samuel Wales
2021-06-11 0:13 ` Samuel Banya
2021-06-11 14:30 ` Juan Manuel Macías
2021-06-11 15:02 ` Samuel Banya
2021-06-09 14:52 ` Maxim Nikulin
2021-06-10 13:28 ` Greg Minshall
2021-06-11 19:51 ` Christian Barthel
2021-06-13 0:46 ` Tim Cross
2021-06-13 15:48 ` Samuel Banya
2021-06-13 23:13 ` Tim Cross
2021-06-09 8:57 ` Eric S Fraga [this message]
2021-06-13 0:31 ` Tim Cross
2021-06-13 4:27 ` Greg Minshall
2021-06-13 7:29 ` Tim Cross
2021-06-14 6:14 ` Greg Minshall
2021-06-07 12:08 ` literate programming, development log -- ideas? Eric S Fraga
2021-06-13 0:24 ` Tim Cross
2021-06-13 15:44 ` Samuel Banya
2021-06-14 12:57 ` Greg Minshall
2021-06-07 13:53 ` Dr. Arne Babenhauserheide
2021-06-07 17:59 ` briangpowell
2021-06-07 23:17 ` Dr. Arne Babenhauserheide
2021-06-08 2:06 ` Samuel Banya
2021-06-08 3:23 ` Greg Minshall
2021-06-08 3:31 ` Samuel Banya
2021-06-08 6:15 ` Greg Minshall
2021-06-08 16:59 ` Greg Minshall
2021-06-07 19:19 ` Jack Kamm
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg1rv2jb.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=minshall@umich.edu \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).