I wanted to follow a convention in naming the vendor branch for a
module, but I goofed, and I now have a vendor branch with a highly
unintuitive name. This vendor branch will, in the future, need to
accept new imports as the vendor releases them. Is there a way for
me to rename the vendor branch so that I won't have to wince every
time I do an import from the vendor?
I'm not worried about screwing up anybody else's checked out version
of the module, because I'm the only one who generally checks it out.
I'm even willing to do some controlled surgery on the contents of the
repository directory if necessary.
Any suggestions?
--
+-------------------------------------------------------------------+
| Dave Makower <[EMAIL PROTECTED]> |
| Manager of Portal Architecture & Development |
+--------------------------------+----------------------------------+
| iClick, Inc. | (914) 872-8030 |
| 120 Bloomingdale Road | (914) 872-8100 fax |
| 3rd Floor | (914) 872-8000 main |
| White Plains, NY 10605 | http://www.iclick.com/ |
+--------------------------------+----------------------------------+
