MySQL Bugs: #27385: bk: using unsupported post-commit trigger

Bug #27385	bk: using unsupported post-commit trigger
Submitted:	22 Mar 2007 20:47	Modified:	27 Mar 2007 9:06
Reporter:	Hakan Küçükyılmaz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Compiling	Severity:	S3 (Non-critical)
Version:		OS:	Linux (Linux)
Assigned to:	Sergei Golubchik	CPU Architecture:	Any

Description:
According to Bitkeeper support we are using unsupported post-commit trigger.

How to repeat:
From the email:

Support:
>> I'm a bit confused. The problem you seem to be having is with
>> "patch". This is not a BitKeeper command. Have you tried pulling from
>> a BK repository?

Me:
> Well, I am confused, too. The patch is generated with bk
> via the BitKeeper/triggers/post-commit script
> using
>   bk changes -v -r+
>   bk cset -r+ -d

Support:
Using bk cset -r+ -d is fragile and unsupported. You either want "bk  
changes -vv -r+" if you're looking for unified diffs, or "bk  
makepatch -r+ -d" if you're looking for a BitKeeper patch.

Note that using unified diffs for moving work is fragil. The patch  
could not apply or be corrupt. It has no integrity checking whatsoever.

Thank you for the report.

Verified as described.

See also "REMOVED INTERFACES" part of cset documentation.

already changed in 5.1