From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] index log
Date: Sat, 22 Aug 2009 06:46:27 -0700 [thread overview]
Message-ID: <1250948551-sup-2052@masanjin.net> (raw)
In-Reply-To: <1250491123-19240-1-git-send-email-rlane@club.cc.cmu.edu>
Reformatted excerpts from Rich Lane's message of 2009-08-16:
> Add a YAML logfile that records changes to the index and modify
> sup-dump to use this rather than the normal database.
I like this. I'm going to wait to apply it until the api refactoring
stuff is merged down to master though. Should be soon.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-08-22 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 6:38 Rich Lane
2009-08-22 13:46 ` William Morgan [this message]
2009-08-24 12:20 ` Nicolas Pouillard
2009-08-31 4:16 ` Rich Lane
2009-08-31 11:42 ` Ben Walton
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=1250948551-sup-2052@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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