-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Frank Hemer wrote:
|> If your second part, above, were abstracted out such that the new |> revision-1 tag could be used anywhere CVS accepts two revision |> options (basically, diff & update/commit -j), then this format |> could also be used to concisely back out a commit or to merge a |> specific commit to a new location. |> |> It's possible that something like `.previous' would be a good |> special tag for this case since it doesn't intrude on the |> existing tag namespace, a la Steve Cameron's .trunk/.parent/.base |> patch that needs to be ported forward and committed someday. | | | Well I would like to take a look at this patch but I cannot find | it, neither in the archives nor with google. Does anybody have an | old copy lying around?
Steve's page has been down for awhile, I think, but I found a reference in the WayBack machine:
<http://web.archive.org/web/20011004170734/http://www.geocities.com/dotslashstar/branch_patch.html>
The most recent version of the patch I could find, also from the wayback machine, is here:
<http://web.archive.org/web/20011004195552/www.geocities.com/dotslashstar/patch.08.29.2001.txt>
I was just glancing at that patch and I think I can implement what Steve did much more succinctly, so I'm going to take a shot at it. The most important thing for your patch is probably to use the naming scheme: `.XXX'.
Cheers,
Derek -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCHe5MLD1OTBfyMaQRAvesAKDXzSlwBL/Ij0A+ia5O2JaOqGv+SgCdFKp/ V67SS63X8K8hc/7zHz/YPnw= =ep8G -----END PGP SIGNATURE-----
_______________________________________________ Bug-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-cvs
