All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elvis Pranskevichus <elprans@gmail.com>
To: Martin Waitz <tali@admingilde.org>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Use git-tag in git-cvsimport
Date: Mon, 4 Jun 2007 19:55:52 -0400	[thread overview]
Message-ID: <200706041955.52779.elprans@gmail.com> (raw)
In-Reply-To: <7v1wgto2mh.fsf@assigned-by-dhcp.cox.net>

> hoi :)

Hi =)

> On Sun, Jun 03, 2007 at 05:01:03PM -0700, Junio C Hamano wrote:
> > Martin Waitz <tali@admingilde.org> writes:
> > > but lightweight tags are not fetched by default.
> > 
> > Are you sure about that?

> not any more now that you questioned it ;-)

Last time I checked, unannotated tags are git-cloned and git-fetched just 
fine. I'm not sure about the exact definition and behaviour of lightweight 
tags, though. 

CVS just doesn't attach any valuable info to the tags, it's just a point in 
time.

> But at least there is a hook script which refuses to receive
> un-annotated tags and I always considered those tags to be temporary
> tags in the local repository.

Well, there's no mention about that in the docs. And I don't think that the 
notion of git losing valid objects along the way is the good one =)

Anyways, the patch wasn't about the tag type change. As I mentioned it's just 
a side effect. The main point is to fix the cvsimport tag breakage. I've 
tested that change on a few big (and messy) CVS repos, and it works just 
fine.

Cheers,
-- 

                 Elvis

  reply	other threads:[~2007-06-04 23:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03  6:56 [PATCH] Use git-tag in git-cvsimport Elvis Pranskevichus
2007-06-03  8:37 ` Junio C Hamano
2007-06-04 23:55   ` Elvis Pranskevichus [this message]
2007-06-03 22:53 ` Martin Waitz
2007-06-04  0:01   ` Junio C Hamano
2007-06-04  7:18     ` Martin Waitz
2007-06-06 20:41       ` Junio C Hamano

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=200706041955.52779.elprans@gmail.com \
    --to=elprans@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=tali@admingilde.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.