From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: should `G r' rename score files?
Date: 16 Sep 2004 09:03:53 -0400 [thread overview]
Message-ID: <4noek6wekm.fsf@lifelogs.com> (raw)
In-Reply-To: <uisaex3yd.fsf@vignette.com> (Kevin Greiner's message of "Wed, 15 Sep 2004 22:55:38 -0500")
On Wed, 15 Sep 2004, kevin.greiner@vignette.com wrote:
> I considered implementing this several months ago. I ended up
> abandoning the effort because of the way that hierarchical score files
> function. I'll use an example to describe the problem.
>
> Let's say that you have the groups:
> a.b.c
> a.b.d
>
> and the score files:
> a.b.c.SCORE
> a.b.d.SCORE
> a.b.SCORE
> a.SCORE
>
> Now, if I rename a.b.c to x.y.z. What do I do about the score files?
>
> Renaming a.b.c.SCORE to x.y.z.SCORE is obvious. The problem is what
> to do with a.b.SCORE and a.SCORE.
>
> The options are:
> * If I do nothing, then the score rules for x.y.z will not match the
> score rules used when the group was named a.b.c.
> * If I rename a.b.SCORE and a.SCORE, then the score rules for a.b.d
> are changed.
> * If I copy a.b.SCORE to x.y.SCORE and a.SCORE to x.SCORE, then these groups
> are OK but what if x.SCORE or x.y.SCORE already existed?
I think the user should be alerted at the time of renaming:
"The score files a.b and a will no longer apply to group x.y.z
(formerly a.b.c). Proceed with group rename? (y/n)"
(abort the rename if necessary) and then
"The score file a.b.c should be renamed to x.y.z. Proceed with score
file rename? (y/n)"
I think that gives the user a chance to do the right thing or at least
know what will be affected.
Ted
next prev parent reply other threads:[~2004-09-16 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 20:02 Dan Christensen
2004-09-16 3:55 ` Kevin Greiner
2004-09-16 13:03 ` Ted Zlatanov [this message]
2004-10-24 13:35 ` Kai Grossjohann
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=4noek6wekm.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).