From: Luben Tuikov <ltuikov@yahoo.com>
To: Andy Parkins <andyparkins@gmail.com>, git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: Errors pushing tags in "next"
Date: Fri, 23 Mar 2007 02:38:41 -0700 (PDT) [thread overview]
Message-ID: <409322.88629.qm@web31809.mail.mud.yahoo.com> (raw)
In-Reply-To: <200703230913.12742.andyparkins@gmail.com>
--- Andy Parkins <andyparkins@gmail.com> wrote:
> The output you show is from the update hook from an older version of git, but
> the git you're running on the remote end is a newer version. The hook
> scripts don't get updated when you upgrade git because they're copied to the
> repository from the latest template when you clone or init.
Yeah, most of my git repos, especially the web exported ones are
truly of an ancient git...
> The fix: My own suggestion would be to just swap the update hook on the
> server for the one that came with the latest version of git (although I'm
> completely biased :-)). Remember to do this on the remote repository, not
> your local one.
Yeah, I'll cp(1) the most recent "update" hook I got in "next" to the
ancient web exported repos I own...
> Alternatively; I've got a further update to the notification email script
> prepared that I'm finishing testing and will send today that updates to use
> the post-receive hook rather than the update hook and fixes a number of bugs.
Ok, sounds good.
Thanks,
Luben
prev parent reply other threads:[~2007-03-23 9:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 2:03 Errors pushing tags in "next" Luben Tuikov
2007-03-23 2:48 ` Junio C Hamano
2007-03-23 3:35 ` Luben Tuikov
2007-03-23 4:18 ` Junio C Hamano
2007-03-23 7:44 ` Luben Tuikov
2007-03-23 8:16 ` Junio C Hamano
2007-03-23 9:02 ` Marco Roeland
2007-03-23 9:17 ` Junio C Hamano
2007-03-23 9:43 ` Luben Tuikov
2007-03-23 9:19 ` Luben Tuikov
2007-03-23 9:13 ` Andy Parkins
2007-03-23 9:38 ` Luben Tuikov [this message]
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=409322.88629.qm@web31809.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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