[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] mail subjects

From: Simon Large <simon_at_skirridsystems.co.uk>
Date: 2005-10-12 11:27:33 CEST

Matthias Wchter wrote:
> Stefan Kng schrieb:
>
>> Did you guys see that? :
>>
>> [TSVN_U] Re: [TSVN] Cannot replace a directory from within
>>
>> That's the downside of using different subject id's for users and dev.
>>
>> I'd like to suggest to simply *remove* those on *all* our lists
>> (users,dev,patches). Mail filtering can be easily done using the 'To:'
>> and 'Cc:' fields.
>
>
> Although I second the idea of removing the prefix I rather suggest to
> use one of the other header fields instead of To and/or CC. This mail,
> for example, is addressed to dev@ and users@ (so two mails arrive) but
> for both copies it will be filtered to _either_ the users' TSVN_DEV
> container or the TSVN_USERS container, depending on which rule to move
> is first.

Doesn't happen often - only because I was transferring to the other
list. This mail is sent only to dev, and I have trimmed the subject this
time ;-)

> Each ezmlm-written mailinglist mail contains the "Mailing-List:" header
> field. This could be evaluated for correct filtering. Alternatives are
> "list-post:" and "Delivered-To:" naming the mailing list address as well
> (without the "-help" appendix).

That works ok in some mail clients, but Microsoft ones are generally too
broken to allow you to use anything but the basic fields.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 12 11:28:01 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.