From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: git@vger.kernel.org
Subject: Re: problems when pushing to a master repository
Date: Thu, 22 Dec 2005 08:56:03 -0200 [thread overview]
Message-ID: <1135248963.17758.18.camel@localhost> (raw)
In-Reply-To: <1135246723.17758.14.camel@localhost>
Em Qui, 2005-12-22 às 08:18 -0200, Mauro Carvalho Chehab escreveu:
> I've started working recently with git, and I'm suffering problems to
> update a master repository. Sometimes, git refuses to update a master
> repository:
>
> git push
> ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/v4l-dvb.git
> master
> error: src refspec master matches more than one.
> fatal: unexpected EOF
>
> Even removing the branch, git-prune and reimporting doesn't work. I
> have to reimport the tree from master repository.
>
> Any sugestions?
I found the problem. git created a refs/bases dir, with old references
with the same names. Removing it fixed the problem.
Cheers,
Mauro.
prev parent reply other threads:[~2005-12-22 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 10:18 problems when pushing to a master repository Mauro Carvalho Chehab
2005-12-22 10:56 ` Mauro Carvalho Chehab [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=1135248963.17758.18.camel@localhost \
--to=mchehab@infradead.org \
--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).