Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [PATCH] Allow toggle on Source.usual and Source.archived
Date: Sat, 15 May 2010 14:45:21 -0400	[thread overview]
Message-ID: <1273949121-16731-1-git-send-email-bwalton@artsci.utoronto.ca> (raw)

Allow sources to be more malleable by allowing for the modification of
the usual and archived flags.  This is a first step toward patterned
(meta) sources.  Initially, the patterning will be handled by one of
the poll hooks, which will use the usual toggle when a 'new' source is
added.  Later on, this may be handled internally for sources with a
meta = true attribute (or something similar).

Signed-off-by: Ben Walton <bwalton@artsci.utoronto.ca>
---
 lib/sup/source.rb |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/lib/sup/source.rb b/lib/sup/source.rb
index 6fe7bfb..2f2e5df 100644
--- a/lib/sup/source.rb
+++ b/lib/sup/source.rb
@@ -63,7 +63,8 @@ class Source
   ##
   ## dirty? means cur_offset has changed, so the source info needs to
   ## be re-saved to sources.yaml.
-  bool_reader :usual, :archived, :dirty
+  bool_reader :dirty
+  bool_accessor :usual, :archived
   attr_reader :uri, :cur_offset
   attr_accessor :id
 
-- 
1.7.0

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


             reply	other threads:[~2010-05-15 18:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-15 18:45 Ben Walton [this message]
2010-06-03  3:58 ` Rich Lane

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=1273949121-16731-1-git-send-email-bwalton@artsci.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    --cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox