unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Bristow <pbristow@bluearc.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "7302@debbugs.gnu.org" <7302@debbugs.gnu.org>
Subject: bug#7302: cliff using "sccs get" rather than "get" breaks bitkeeper usage.
Date: Mon, 1 Nov 2010 08:44:34 +0000	[thread overview]
Message-ID: <ABFC24E4C13D81489F7F624E14891C860992D6D98F@uk-ex-mbx1.terastack.bluearc.com> (raw)
In-Reply-To: <jwvzktx0w95.fsf-monnier+emacs@gnu.org>

Thanks for the quick response.  I have tried that patch and can confirm that it works for me.
Regards,
  Paul.


-----Original Message-----
From: Stefan Monnier [mailto:monnier@iro.umontreal.ca] 
Sent: 29 October 2010 18:09
To: Paul Bristow
Cc: 7302@debbugs.gnu.org
Subject: Re: bug#7302: vcdiff using "sccs get" rather than "get" breaks bitkeeper usage.

> I previously used Emacs 21.4 and its version of the vcdiff script is
> compatible with bk as it just calls "get" and bitkeeper supplies a get
> command.  In 23.2.1 the command is "sccs get" but there is no sccs
> with bitkeeper.
[...]
> I have found that reverting to the old behaviour with the patch that
> I have included below solves the problem.

But using just `get' won't work with CSSC, for example.

> Perhaps the change might be reverted or parameterised in
> future releases?

We could first try `sccs get' and if that fails fallback on `get'.
Can you confirm that the patch below works for you?


        Stefan


=== modified file 'lib-src/vcdiff'
--- lib-src/vcdiff	2010-01-13 08:35:10 +0000
+++ lib-src/vcdiff	2010-10-29 17:08:47 +0000
@@ -79,6 +79,12 @@
 trap 'status=2; exit' 1 2 13 15
 trap 'rm -f $rev1 $rev2 || status=2; exit $status' 0
 
+if ! type sccs >/dev/null 2>&1 && type get >/dev/null 2>&1 ; then
+    sccsget="get"
+else
+    sccsget="sccs get"
+fi
+
 for f
 do
 	s=2
@@ -87,14 +93,14 @@
 	s.* | */s.*)
 		if
 			rev1=`mktemp /tmp/geta.XXXXXXXX`
-			sccs get -s -p -k $sid1 "$f" > $rev1 &&
+			$sccsget -s -p -k $sid1 "$f" > $rev1 &&
 			case $sid2 in
 			'')
 				workfile=`expr " /$f" : '.*/s.\(.*\)'`
 				;;
 			*)
 				rev2=`mktemp /tmp/getb.XXXXXXXX`
-				sccs get -s -p -k $sid2 "$f" > $rev2
+				$sccsget -s -p -k $sid2 "$f" > $rev2
 				workfile=$rev2
 			esac
 		then






  reply	other threads:[~2010-11-01  8:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 15:21 bug#7302: vcdiff using "sccs get" rather than "get" breaks bitkeeper usage Paul Bristow
2010-10-29 16:51 ` Glenn Morris
2010-10-29 17:09 ` Stefan Monnier
2010-11-01  8:44   ` Paul Bristow [this message]
2011-03-15  6:26     ` Glenn Morris
2011-03-15 13:19       ` Stefan Monnier
2012-06-06  0:33         ` Glenn Morris
2011-03-15 15:23       ` Oscar Bonilla
2016-02-26  6:29         ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ABFC24E4C13D81489F7F624E14891C860992D6D98F@uk-ex-mbx1.terastack.bluearc.com \
    --to=pbristow@bluearc.com \
    --cc=7302@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).