From: Luben Tuikov <ltuikov@yahoo.com>
To: Marco Roeland <marco.roeland@xs4all.nl>, Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Errors pushing tags in "next"
Date: Fri, 23 Mar 2007 02:19:52 -0700 (PDT) [thread overview]
Message-ID: <803772.83961.qm@web31809.mail.mud.yahoo.com> (raw)
In-Reply-To: <20070323090213.GA7186@fiberbit.xs4all.nl>
--- Marco Roeland <marco.roeland@xs4all.nl> wrote:
> On Friday March 23rd 2007 at 01:16 Junio C Hamano wrote:
>
> > Luben Tuikov <ltuikov@yahoo.com> writes:
> >
> > > BTW, git has always said to me "Pushing version ... to the masses"
> > > whenever I'd do "git-push --tags web".
> >
> > Sorry, I must be blind, and git-grep is too.
> >
> > $ git grep -e 'to the masses' -e 'Pushing v'
> >
> > returns absolutely empty.
>
> The line comes from an older version of templates/hooks--update. The
> line was removed in commit 829a686f1b50ba96cac2d88494fa339efe0c0862 .
>
> So Luben does seem to have a hook installed, perhaps this is the
> culprit.
I see.
I double checked and I do have "update" and "post-update" hooks
enabled. I don't think that it is "post-update" and this leaves
"update" to be the problem (which is from an ancient git version
when the repo was created...).
I'll update the "update" hook from a recent git version and
will see if I get the same warning message. Hopefully not.
Thanks,
Luben
next prev parent reply other threads:[~2007-03-23 9:19 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 [this message]
2007-03-23 9:13 ` Andy Parkins
2007-03-23 9:38 ` Luben Tuikov
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=803772.83961.qm@web31809.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=marco.roeland@xs4all.nl \
/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