From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Goals for repo conversion day
Date: Sat, 25 Jan 2014 23:08:21 +0100 [thread overview]
Message-ID: <87bnyzemui.fsf@zigzag.favinet> (raw)
In-Reply-To: <20140125195401.GA13305@thyrsus.com> (Eric S. Raymond's message of "Sat, 25 Jan 2014 14:54:01 -0500")
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
() "Eric S. Raymond" <esr@thyrsus.com>
() Sat, 25 Jan 2014 14:54:01 -0500
That is true. But beware of misleading analogies! Archeologists
like the seams mainly because stratigraphy helps them date things.
Repo contents is first order information. Higher order is: What are
the structures that hold the repo contents (i.e., what is the VCS)?;
What are the factors in its choice?; Why are hackers so human?; ...
This is a problem historians looking through a version-control
repository won't have.
Right. They will have this problem from the extra-repo references in
mailing list archives (public and private), bug tracker databases,
blogs, etc. If you really want to help historians, the maps (and tools)
will be what they will thank you for the most, for the insight afforded.
(Insert Alan Perlis quote here.)
Historians might thank you, anyway, for an "antiseptic" repo, but
privately refer to an unsullied copy, for the Real Deal, a place where
Free and Hippocratic programs are composed and run (composably :-D).
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-01-25 22:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 16:29 The git mirror is *very* badly screwed up Eric S. Raymond
2014-01-24 16:42 ` Andreas Schwab
2014-01-24 17:07 ` Eric S. Raymond
2014-01-24 17:22 ` Andreas Schwab
2014-01-24 18:54 ` Eric S. Raymond
2014-01-24 20:03 ` Eric S. Raymond
2014-01-24 21:06 ` Andreas Schwab
2014-01-24 21:27 ` Eli Zaretskii
2014-01-25 6:25 ` Eric S. Raymond
2014-01-25 7:44 ` Eli Zaretskii
2014-01-25 14:06 ` Goals for repo conversion day Eric S. Raymond
2014-01-25 14:42 ` Eli Zaretskii
2014-01-25 14:46 ` Eli Zaretskii
2014-01-25 16:01 ` Eric S. Raymond
2014-01-25 16:15 ` Paul Eggert
2014-01-25 17:15 ` Eli Zaretskii
2014-01-25 21:01 ` Eric S. Raymond
2014-01-26 17:32 ` Eli Zaretskii
2014-01-27 0:33 ` Eric S. Raymond
2014-01-27 5:16 ` Werner LEMBERG
2014-01-27 16:31 ` Eli Zaretskii
2014-01-27 17:42 ` Werner LEMBERG
2014-01-27 17:54 ` Eli Zaretskii
2014-01-27 10:04 ` Andreas Schwab
2014-01-27 13:22 ` Eric S. Raymond
2014-01-28 8:14 ` Ulrich Mueller
2014-01-28 8:58 ` Andreas Schwab
2014-01-28 9:07 ` David Kastrup
2014-01-28 15:40 ` What to do about the attic files Eric S. Raymond
2014-01-27 16:25 ` Goals for repo conversion day Eli Zaretskii
2014-01-27 16:28 ` Bzr's "confusion" between branches and repositories Eli Zaretskii
2014-01-27 16:47 ` Andreas Schwab
2014-01-27 16:53 ` Eli Zaretskii
2014-01-27 17:15 ` Eli Zaretskii
2014-01-25 19:32 ` Goals for repo conversion day Glenn Morris
2014-01-25 16:09 ` Andreas Schwab
2014-01-25 17:01 ` Thien-Thi Nguyen
2014-01-25 19:54 ` Eric S. Raymond
2014-01-25 22:08 ` Thien-Thi Nguyen [this message]
2014-01-26 3:24 ` Eric S. Raymond
2014-01-25 21:57 ` The git mirror is *very* badly screwed up Stefan Monnier
2014-01-25 23:27 ` Eric S. Raymond
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=87bnyzemui.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.