head	1.4;
access;
symbols;
locks; strict;
comment	@# @;


1.4
date	2002.04.17.08.23.34;	author sobomax;	state Exp;
branches;
next	1.3;

1.3
date	2001.12.30.08.46.21;	author sobomax;	state Exp;
branches;
next	1.2;

1.2
date	2001.12.27.13.07.59;	author sobomax;	state Exp;
branches;
next	1.1;

1.1
date	2001.12.27.13.00.18;	author sobomax;	state Exp;
branches;
next	;


desc
@@


1.4
log
@Remove LIFO/FIFO issue - it seems that I have already resolved it.
@
text
@o Add a distinct marker between "preamble" and the copy of the original
  commit message. This should make parsing of the notification message by
  automatic scripts (such as cvsmerge) easier. Requested by Garance A Drosihn
  <drosih@@rpi.edu>.

o Provide better granularity for sending notifications. Currently granularity
  is 1 day, so that if the person did a commit a hour before "time X" when
  the handler is sheduled to run, and specified "MFC after: 1 day" then he
  will receive notification after a hour instead of after 1 day. Requested by
  Luigi Rizzo <luigi@@FreeBSD.org>.
  NOTE: I'm (sobomax) not really sure that this feature is worth the trouble.


$FreeBSD$
@


1.3
log
@Remove already implemented feature.
@
text
@a5 6
o Ensure that the notifications are being sent in the same order as the
  commits, i.e. if the person does several sequental commits to the same
  file and specifies exactly the same "MFC after" interval he should receive
  notifications in the right order (FIFO). Seemingly current behaviour is
  opposite - LIFO. Reported by Rober Watson <rwarson@@FreeBSD.org>.

@


1.2
log
@Add another TODO item from my archives.
@
text
@d1 4
a4 5
o Extend the notification message with the branch the original commit was for
  as well as add a distinct marker between "preamble" and the copy of the
  original commit message. This should make parsing of the notification
  message by automatic scripts (such as cvsmerge) easier. Requested by
  Garance A Drosihn <drosih@@rpi.edu>.
@


1.1
log
@Add TODO list.
@
text
@d1 6
@

