From: Pete/Piet Delaney <pete@bluelane.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Piet Delaney <piet.delaney@gmail.com>,
Piet Delaney <pdelaney@bluelane.com>
Subject: can't read "treediffs(....)
Date: Wed, 20 Feb 2008 15:18:50 -0800 [thread overview]
Message-ID: <47BCB55A.4090308@bluelane.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
What does this mean?
- -----------------------------------------------------------------------
can't read "treediffs(1c977462d86c94cd20492c72f2be175a05aad0f4)": no
such element in array
can't read "treediffs(1c977462d86c94cd20492c72f2be175a05aad0f4)": no
such element in array
~ while executing
"lindex $treediffs($diffids) [expr {$l-2}]"
~ (procedure "pop_flist_menu" line 11)
~ invoked from within
"pop_flist_menu .bright.cfiles 977 652 54 105"
~ (command bound to event)
- -------------------------------------------------------------------------
- -piet
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHvLVaJICwm/rv3hoRAkjHAJ46mxx+CzdiWHnE5xE/oJ2DR3gNKgCdHSCg
nPffcBjtolA1XIp3F7fWL1U=
=wbMX
-----END PGP SIGNATURE-----
reply other threads:[~2008-02-20 23:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47BCB55A.4090308@bluelane.com \
--to=pete@bluelane.com \
--cc=git@vger.kernel.org \
--cc=pdelaney@bluelane.com \
--cc=piet.delaney@gmail.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.