Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Anirudh Sanjeev <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue57] Request: Flush changes periodically
Date: Thu, 28 Jan 2010 20:06:04 +0000	[thread overview]
Message-ID: <1264709164.82.0.12859120302.issue57@masanjin.net> (raw)
In-Reply-To: <1264709164.82.0.12859120302.issue57@masanjin.net>


New submission from Anirudh Sanjeev <anirudh@anirudhsanjeev.org>:

Can there be an optional functionality to flush changes to disk every 10-15
minutes, instead of having to press $ every time

Rationale: I'm in a place where power cuts are extremely frequent. I keep
forgetting to flush changes manually requiring me to re-delete and archive my
messages every time I reboot and restart sup.

I run sup off of git 'next' head. A patch which will hard-code this
functionality would be fine as well. Alternatively, is there a command I can
call via a cron job to do this?

Thanks!

----------
messages: 142
nosy: anirudhs
priority: feature request
ruby_version: 1.8
status: unread
sup_version: git/next
title: Request: Flush changes periodically

_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue57>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


       reply	other threads:[~2010-01-28 20:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 20:06 Anirudh Sanjeev [this message]
2010-01-28 20:21 ` Eric Sherman

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=1264709164.82.0.12859120302.issue57@masanjin.net \
    --to=sup-bugs@masanjin.net \
    --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