From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] some internal api refactors
Date: Sun, 16 Aug 2009 14:44:49 -0700 [thread overview]
Message-ID: <1250459019-sup-6390@masanjin.net> (raw)
In-Reply-To: <1250054282-sup-9053@pion.club.cc.cmu.edu>
Reformatted excerpts from Rich Lane's message of 2009-08-11:
> It's worth noting that update_message_state needs to handle modified
> refs and snippets as well as labels. Maybe add a comment about this in
> BaseIndex?
Different snippet, definitely. Good point. Modified refs: I'm tempted to
replace this with another API call, since we don't really care about the
refs; we just want the index to thread the messages together. Thoughts?
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-08-16 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 20:14 William Morgan
2009-08-12 5:26 ` Rich Lane
2009-08-16 21:44 ` William Morgan [this message]
2009-08-16 22:49 ` Rich Lane
2009-08-17 19:39 ` William Morgan
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=1250459019-sup-6390@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