http://bugzilla.spamassassin.org/show_bug.cgi?id=3755
--- Additional Comments From [EMAIL PROTECTED] 2005-07-23 07:53 ---
Created an attachment (id=3033)
-- (http://bugzilla.spamassassin.org/attachment.cgi?id=3033action=view)
Added use_language conf setting
--- You are
http://bugzilla.spamassassin.org/show_bug.cgi?id=3755
--- Additional Comments From [EMAIL PROTECTED] 2005-07-23 07:59 ---
(In reply to comment #3)
Morten, your proposal sounds good to me (not a dev). Hoping you'll follow
through, I've updated the milestone to Future and changing
http://bugzilla.spamassassin.org/show_bug.cgi?id=3755
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- You are
http://bugzilla.spamassassin.org/show_bug.cgi?id=4496
Summary: FPS with FORGED_MUA_OIMO
Product: Spamassassin
Version: 3.1.0
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P5
I think it's time to branch 3.1 (also so Justin, Dan, Michael and I
can get some work done while we're here). Votes?
+1
--
Duncan Findlay
signature.asc
Description: Digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Parker writes:
Duncan Findlay wrote:
I think it's time to branch 3.1 (also so Justin, Dan, Michael and I
can get some work done while we're here). Votes?
+1
+1
+1
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
http://bugzilla.spamassassin.org/show_bug.cgi?id=3721
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://taint.org/xfer/2005/google.jpg
+1
--
Daniel Quinlan
http://www.pathname.com/~quinlan/
http://bugzilla.spamassassin.org/show_bug.cgi?id=4448
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|use_dcc and use_pyzor fail |[review] use_dcc and
http://bugzilla.spamassassin.org/show_bug.cgi?id=4425
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|critical|normal
--- Additional
http://bugzilla.spamassassin.org/show_bug.cgi?id=4464
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|major |trivial
--- Additional
http://bugzilla.spamassassin.org/show_bug.cgi?id=4344
--- Additional Comments From [EMAIL PROTECTED] 2005-07-23 15:16 ---
this needs one more +1
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4419
--- Additional Comments From [EMAIL PROTECTED] 2005-07-23 15:18 ---
+1
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4321
--- Additional Comments From [EMAIL PROTECTED] 2005-07-23 15:18 ---
I think henry's right. suggest closing as WFM
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the
Now that we have branched 3.1, trunk is back in CTR mode
(commit-then-review). 3.1 is in RTC mode (review-then-commit) as is
standard for branches (except for masses/ and tests/ which are CTR).
Daniel
--
Daniel Quinlan
http://www.pathname.com/~quinlan/
I propose we keep any change that might break the trunk longer than an
hour in a separate branch as long as necessary.
How do you do that?
svn copy -m creating temporary branch for foo project \
$repo/trunk \
$repo/branches/name/
where name is exp-projectname or exp-username. And
http://bugzilla.spamassassin.org/show_bug.cgi?id=692
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.1.0 |Future
--- You are
http://bugzilla.spamassassin.org/show_bug.cgi?id=2307
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.1.0 |3.1.1
--- You are
http://bugzilla.spamassassin.org/show_bug.cgi?id=2307
[EMAIL PROTECTED] changed:
What|Removed |Added
AssignedTo|spamassassin- |[EMAIL PROTECTED]
http://bugzilla.spamassassin.org/show_bug.cgi?id=3563
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.1.0 |3.1.1
--- You are
On Sat, Jul 23, 2005 at 03:32:08PM -0700, Dan Quinlan wrote:
I propose we keep any change that might break the trunk longer than an
hour in a separate branch as long as necessary.
An alternative is to create a bug and get review prior to committing
your large change.
+1 to make this
http://bugzilla.spamassassin.org/show_bug.cgi?id=3714
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.1.0 |3.2.0
--- Additional
Theo Van Dinter [EMAIL PROTECTED] writes:
Can you better define might break the trunk? Technically any change
could break trunk, but I think you're specifically talking about complex
changes since you mentioned large change. I'd feel better if that
were quantified, and want to make sure
http://bugzilla.spamassassin.org/show_bug.cgi?id=4497
Summary: reorganise PerMsgStatus code
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
http://bugzilla.spamassassin.org/show_bug.cgi?id=4487
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|minor |trivial
--- Additional
http://bugzilla.spamassassin.org/show_bug.cgi?id=4161
--- Additional Comments From [EMAIL PROTECTED] 2005-07-23 16:13 ---
2 issues here:
- umask of lock file
- changing groups
I think the first one is doable for 3.1.0. The second one may be a duplicate of
bug 3871.
--- You
http://bugzilla.spamassassin.org/show_bug.cgi?id=4344
--- Additional Comments From [EMAIL PROTECTED] 2005-07-23 16:15 ---
+1
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4344
--- Additional Comments From [EMAIL PROTECTED] 2005-07-23 16:15 ---
+1
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4363
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.1.0 |3.2.0
--- Additional
http://bugzilla.spamassassin.org/show_bug.cgi?id=4344
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://bugzilla.spamassassin.org/show_bug.cgi?id=4364
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.1.0 |3.1.1
--- Additional
http://bugzilla.spamassassin.org/show_bug.cgi?id=4364
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.1.1 |3.1.0
--- Additional
http://bugzilla.spamassassin.org/show_bug.cgi?id=4408
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://bugzilla.spamassassin.org/show_bug.cgi?id=4419
--- Additional Comments From [EMAIL PROTECTED] 2005-07-23 16:55 ---
+1
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4425
[EMAIL PROTECTED] changed:
What|Removed |Added
Attachment #2953|application/octet-stream|text/plain
mime type|
http://bugzilla.spamassassin.org/show_bug.cgi?id=4426
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.1.0 |3.1.1
--- Additional
http://bugzilla.spamassassin.org/show_bug.cgi?id=4427
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.1.0 |3.2.0
--- Additional
http://bugzilla.spamassassin.org/show_bug.cgi?id=4448
--- Additional Comments From [EMAIL PROTECTED] 2005-07-23 17:37 ---
+1
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4464
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.1.0 |3.0.5
--- Additional
The last update to the 3.10 snapshots seems to be posted on July 17:
http://cvs.apache.org/snapshots/spamassassin/
The downloads page in the SA project doesn't list any releases for 3.10 yet:
http://spamassassin.apache.org/downloads.cgi?update=200506061100
Is there are more appropriate
http://bugzilla.spamassassin.org/show_bug.cgi?id=4479
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.1.0 |3.1.1
--- You are
http://bugzilla.spamassassin.org/show_bug.cgi?id=4491
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||dev@spamassassin.apache.org
http://bugzilla.spamassassin.org/show_bug.cgi?id=4129
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
http://bugzilla.spamassassin.org/show_bug.cgi?id=4138
[EMAIL PROTECTED] changed:
What|Removed |Added
Keywords||moreinfo, triage
Target
http://bugzilla.spamassassin.org/show_bug.cgi?id=4263
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://bugzilla.spamassassin.org/show_bug.cgi?id=4484
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|major |normal
Keywords|triage
http://bugzilla.spamassassin.org/show_bug.cgi?id=3884
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://bugzilla.spamassassin.org/show_bug.cgi?id=4342
[EMAIL PROTECTED] changed:
What|Removed |Added
Keywords|triage |
Target Milestone|Undefined
http://bugzilla.spamassassin.org/show_bug.cgi?id=4352
--- Additional Comments From [EMAIL PROTECTED] 2005-07-23 20:01 ---
Created an attachment (id=3034)
-- (http://bugzilla.spamassassin.org/attachment.cgi?id=3034action=view)
Rules used to test for improvements
Attached are some
http://bugzilla.spamassassin.org/show_bug.cgi?id=4352
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|Undefined |3.2.0
--- You are
Just thought I'd post a quick note about the hackathon that took place
today at Stanford university. We below refers to Justin Mason,
Daniel Quinlan, Michael Parker and me. Matt Sergeant was also present
too for a while, so we can include him too for some of the
following items. :-)
Discussion
I know user rules aren't real popular with the sa dev community, however
that attitude isn't universally shared by sa users. Therefore may I
suggest:
Would it be possible when reorganizing things to come up with some
semi-persistant storage for compiled user rules, so that they don't have to
be
53 matches
Mail list logo