From: Gaurav Chhabra <varuag.chhabra@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Error pushing new branch: value too great for base (error token is...
Date: Wed, 5 Aug 2015 23:02:26 +0530 [thread overview]
Message-ID: <CAGDgvc3Gxn=pKBfYC+yrUhCmL9X6bqjPVwVokF0qPsXmhx_EaQ@mail.gmail.com> (raw)
I had written the following code to check whether a push is for branch deletion:
#!/bin/bash
NULL="0000000000000000000000000000000000000000"
while read old_sha new_sha refname ; do
echo "Stdin: [$old_sha] [$new_sha] [$refname]"
if [[ "$new_sha" -eq "$NULL" ]]; then # Line 17
echo "Skipping checks..."
continue
fi
...
...
...
done
While it works fine for branch deletion, i noticed that if i create a
branch and push it to remote, i get the following error due to the
above-mentioned code:
$ git push origin rel-a
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 407 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: Stdin: [0000000000000000000000000000000000000000]
[9226289d2416af4cb7365d7aaa5e382bdb3d9a89] [refs/heads/rel-a]
remote:
remote: hooks/pre-receive: line 17: [[:
9226289d2416af4cb7365d7aaa5e382bdb3d9a89: value too great for base
(error token is "922628
9d2416af4cb7365d7aaa5e382bdb3d9a89")
Although the new branch gets pushed to remote but i'm not sure why i'm
getting this error and how can i fix it. I checked online and i get
few links where folks had similar issue but in each such case, the
error token was 08 or 09. I still tried the suggestion of using "10#"
in front of my $new_sha variable but to no avail.
Any suggestions?
next reply other threads:[~2015-08-05 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 17:32 Gaurav Chhabra [this message]
2015-08-05 17:53 ` Error pushing new branch: value too great for base (error token is Eric Sunshine
[not found] ` <CAGDgvc2hc+f5CuPXc2pr5uYd9kniVpuffrb6z416CicxBgVxJQ@mail.gmail.com>
2015-08-10 9:54 ` Gaurav Chhabra
2015-08-10 22:29 ` Jacob Keller
2015-08-10 22:47 ` Eric Sunshine
2015-08-11 6:30 ` Gaurav Chhabra
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='CAGDgvc3Gxn=pKBfYC+yrUhCmL9X6bqjPVwVokF0qPsXmhx_EaQ@mail.gmail.com' \
--to=varuag.chhabra@gmail.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).