From: Jorge Godoy <godoy@ieee.org>
Cc: ding@gnus.org
Subject: Re: Expiring and keeping marks
Date: Thu, 03 Oct 2002 14:45:47 -0300 [thread overview]
Message-ID: <kpbs6b1kms.fsf@wintermute.casa> (raw)
In-Reply-To: <87k7kz8rr4.fsf@crybaby.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Thu, 03 Oct 2002 17:30:07 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Maybe the function can be changed to move the message instead of
> doing delete/add.
It would help. The idea o copying and deleting at filesystem level
should still be used to avoi problems of moving data between
filesystems. Just moving the entries in .overview and .marks should be
enough.
--
Godoy. <godoy@ieee.org>
next prev parent reply other threads:[~2002-10-03 17:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 12:03 Jorge Godoy
2002-10-03 15:00 ` Mike Woolley
2002-10-03 15:30 ` Kai Großjohann
2002-10-03 17:45 ` Jorge Godoy [this message]
2002-12-29 15:27 ` Lars Magne Ingebrigtsen
2002-12-30 13:49 ` Jorge Godoy
2002-12-30 14:08 ` Jorge Godoy
2002-12-30 15:51 ` Lars Magne Ingebrigtsen
2003-01-02 17:23 ` Simon Josefsson
2003-01-02 18:38 ` Lars Magne Ingebrigtsen
2002-12-31 9:05 ` Mike Woolley
2003-01-01 19:01 ` Lars Magne Ingebrigtsen
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=kpbs6b1kms.fsf@wintermute.casa \
--to=godoy@ieee.org \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).