Devrim GÜNDÜZ <devrim at gunduz.org> writes:
> On Thu, 2009-02-19 at 11:31 -0500, Christopher Browne wrote:
>> > It might be good to rename it before we ship 2.0.1.
>> 
>> This, regrettably, results from us having a Slonik command with
>> exactly the same name as an SQL command.
>> 
>> The following patch shifts the filename, but I don't entirely love it
>> as an answer, as the filename becomes a little bit misleading.
>> 
>> I think it'll do, though.  Do you think that seems OK?
>
> If we are gonna do it, why don't we rename all *files*, but keep the
> command the same?

I think I like better the notion of renaming the <refentrytitle> value
to include the word SLONIK.  Given that, we get the following, which
resolves the conflicts pretty clearly:

chris at dba2:CMD/slony1-2.0/doc/adminguide> ls -w 80 man7
ADMIN CONNINFO.7	 SLONIK EXIT.7		      SLONIK SLEEP.7
CLONE FINISH.7		 SLONIK FAILOVER.7	      SLONIK STORE LISTEN.7
CLONE PREPARE.7		 SLONIK INIT CLUSTER.7	      SLONIK STORE NODE.7
CLUSTER NAME.7		 SLONIK LOCK SET.7	      SLONIK STORE     PATH.7
DEFINE.7		 SLONIK MERGE     SET.7       SLONIK STORE TRIGGER.7
ECHO.7			 SLONIK MOVE SET.7	      SLONIK SUBSCRIBE SET.7
INCLUDE.7		 SLONIK REPAIR CONFIG.7       SLONIK SYNC.7
SLONIK CREATE SET.7	 SLONIK RESTART NODE.7	      SLONIK TABLE ADD KEY.7
SLONIK DROP LISTEN.7	 SLONIK SET ADD SEQUENCE.7    SLONIK UNINSTALL NODE.7
SLONIK DROP NODE.7	 SLONIK SET ADD TABLE.7       SLONIK UNLOCK SET.7
SLONIK DROP PATH.7	 SLONIK SET DROP SEQUENCE.7   SLONIK UNSUBSCRIBE SET.7
SLONIK DROP SET.7	 SLONIK SET DROP TABLE.7      SLONIK UPDATE FUNCTIONS.7
SLONIK DROP TRIGGER.7	 SLONIK SET MOVE SEQUENCE.7   SLONIK WAIT FOR EVENT.7
SLONIK EXECUTE SCRIPT.7  SLONIK SET MOVE     TABLE.7

-- 
output = reverse("ofni.secnanifxunil" "@" "enworbbc")
http://linuxdatabases.info/info/linuxxian.html
Customer: "I'm running Windows '95." 
Tech: "Yes." 
Customer: "My computer isn't working now." 
Tech: "Yes, you said that."