linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bitkeeper@bitkeeper.com
To: linuxppc-dev@lists.linuxppc.org, lm@bitmover.com, bitkeeper@bitmover.com
Subject: BK BUG: Bad fudges should be caught in commit trigger
Date: Sun, 20 Jan 2002 03:13:14 -0800 (PST)	[thread overview]
Message-ID: <20020120111314.940A81008D@hostme.bitkeeper.com> (raw)


View Bug:

http://bitkeeper.bitkeeper.com/cgi-bin/bugview?open/2002-01-20-001

Bug ID:
	2002-01-20-001

Submitter:
	lm@bitmover.com

Type:
	RFE

Summary:
	Bad fudges should be caught in commit trigger

Severity:
	3

Priority:
	4

Status:
	open

Program:
	delta

Release:
	BitKeeper version is 20020117053606 for x86-glibc22-linux

OS:
	Linux work.bitmover.com 2.4.9-13 #1 Tue Oct 30 20:05:14 EST 2001 i686 unknown


Interest:
	linuxppc-dev@lists.linuxppc.org
lm@bitmover.com,bitkeeper@bitmover.com

Description:

Suppose we have a system where time goes backwards or really far
forwards.  When we go to do the commit, we could have a time
sanity trigger which flags this as a possible error and asks them
to go fix their clocks before doing the checkin.


Suggestion:
	This really wants to be a pre-delta trigger and it needs to work from
citool as well as the command line.  So we have to pass state to it
to tell it that it is a GUI app and we need a way to get a yes/no
from the pop up.
As for the time itself, if the time goes backwards more than a day,
flag that, and if it goes forward for more than a month, flag that.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2002-01-20 11:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020120111314.940A81008D@hostme.bitkeeper.com \
    --to=bitkeeper@bitkeeper.com \
    --cc=bitkeeper@bitmover.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=lm@bitmover.com \
    /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).