From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Theodore Tso <tytso@mit.edu>, Junio C Hamano <junkio@cox.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
James Bowes <jbowes@dangerouslyinc.com>,
Johannes.Schindelin@gmx.de
Subject: Re: [PATCH] Make gc a builtin.
Date: Wed, 14 Mar 2007 10:45:55 +0000 [thread overview]
Message-ID: <200703141045.58739.andyparkins@gmail.com> (raw)
In-Reply-To: <20070314074440.GC12710@thunk.org>
On Wednesday 2007 March 14 07:44, Theodore Tso wrote:
> I agree with Junio; I think the scripts are much more readable and
> easier to understand; In fact, it would be nice if the script were
> preserved somewhere, perhaps as comments in the .c file.
If only there were some tool that would keep collections of files as a
snapshotted whole and allow us to browse the history of those snapshots in
some sort of connected graph, with each snapshot being given some sort of
unique ID. Then we could simply refer to that unique ID when we wanted to
tell someone about a particular historical instance.
:-)
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-03-14 10:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 1:58 [PATCH] Make gc a builtin James Bowes
2007-03-14 6:07 ` Shawn O. Pearce
2007-03-14 7:19 ` Junio C Hamano
2007-03-14 7:44 ` Theodore Tso
2007-03-14 7:55 ` Santi Béjar
2007-03-14 9:29 ` Junio C Hamano
2007-03-14 10:45 ` Andy Parkins [this message]
2007-03-14 11:12 ` Junio C Hamano
2007-03-14 11:48 ` Andy Parkins
2007-03-14 12:19 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2007-03-13 23:03 James Bowes
2007-03-14 1:05 ` Johannes Schindelin
2007-03-14 1:37 ` Brian Gernhardt
2007-03-11 22:06 [PATCH 0/2] " James Bowes
2007-03-11 22:06 ` [PATCH 2/2] " James Bowes
2007-03-11 22:48 ` Johannes Schindelin
2007-03-12 2:11 ` Junio C Hamano
2007-03-12 2:51 ` [PATCH] " James Bowes
2007-03-12 14:43 ` Shawn O. Pearce
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=200703141045.58739.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jbowes@dangerouslyinc.com \
--cc=junkio@cox.net \
--cc=spearce@spearce.org \
--cc=tytso@mit.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.
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 NNTP newsgroup(s).