git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yann Dirson <ydirson@altern.org>
To: Christian Biesinger <cbiesinger@web.de>
Cc: GIT list <git@vger.kernel.org>
Subject: Re: [PATCH] Ignore commits for which cvsps can't identify a branch
Date: Sat, 10 Jun 2006 21:24:57 +0200	[thread overview]
Message-ID: <20060610192457.GA6620@nowhere.earth> (raw)
In-Reply-To: <200602102102.k1AL2Xkd010415@biesi.no-ip.org>

On Fri, Feb 10, 2006 at 10:02:33PM +0100, Christian Biesinger wrote:
> cvps sometimes can't identify a branch for a specific revision, it shows
> messages like:
>   WARNING: revision 1.36.2.2 of file Makefile.in on unnamed branch
> and uses #CVSPS_NO_BRANCH as branch name in its output.

This issue is a bit old, but still...

I have seen such CVSPS_NO_BRANCH things with "cvsps -u", and could
always get rid of it using "cvspx -x".  Christian, did you try to run
"cvsps -x" to be sure the cache is valid, and did it get rid of the
CVSPS_NO_BRANCH ?  It could help if you could make a cvsps cache
available, which exhibits the problem.

Best regards,
-- 
Yann Dirson    <ydirson@altern.org> |
Debian-related: <dirson@debian.org> |   Support Debian GNU/Linux:
                                    |  Freedom, Power, Stability, Gratis
     http://ydirson.free.fr/        | Check <http://www.debian.org/>

  parent reply	other threads:[~2006-06-10 19:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10 21:02 [PATCH] Ignore commits for which cvsps can't identify a branch Christian Biesinger
2006-02-10 21:21 ` Junio C Hamano
2006-02-10 22:02   ` Christian Biesinger
2006-02-10 23:25     ` Linus Torvalds
2006-06-10 19:24 ` Yann Dirson [this message]
2006-06-10 19:45   ` Christian Biesinger

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=20060610192457.GA6620@nowhere.earth \
    --to=ydirson@altern.org \
    --cc=cbiesinger@web.de \
    --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).