From: Frank Sorenson <frank@tuxrocks.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Kernel git tree problem? gitk problem?
Date: Sat, 18 Jun 2005 18:12:44 -0600 [thread overview]
Message-ID: <42B4B87C.2000007@tuxrocks.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
With the new crop of post-2.6.12 updates, my kernel trees (tested on
several computers, and even with brand-new tree) now give the following
error messages when I run gitk:
ERROR: none of the pending commits can be done yet:
bd6ae2f6d61da0f90c6b66e9a4ab6c53ef8c159a
2512809255d018744fe6c2f5e996c83769846c07
88d7bd8cb9eb8d64bf7997600b0d64f7834047c5
b3214970abbe983cd89842ae24ea00e21bba79f6
git-fsck-cache doesn't appear to know about any problems.
Is this a gitk problem, or is there something wrong with the tree?
What is a "pending commit?" Is that a commit that hasn't been
committed, or something? :)
Thanks,
Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
frank@tuxrocks.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCtLh8aI0dwg4A47wRAscuAJ4ut87UDbYimUbfxmYT06e1AlNpMwCeIGrA
wgDmnq31zPOcPEZr67BOb4E=
=rdnC
-----END PGP SIGNATURE-----
reply other threads:[~2005-06-19 0:07 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=42B4B87C.2000007@tuxrocks.com \
--to=frank@tuxrocks.com \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).