git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Andreas Ericsson <ae@op5.se>
Cc: git@vger.kernel.org
Subject: Re: Pulling tags from git.git
Date: Mon, 20 Mar 2006 19:30:18 +0100	[thread overview]
Message-ID: <87lkv5ynnp.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <441064DD.2010903@op5.se> (Andreas Ericsson's message of "Thu, 09 Mar 2006 18:24:45 +0100")

* Andreas Ericsson:

>> The current implementation is rather counter-intuitive because it's
>> much easier to create lightweight tags, and you wonder why they aren't
>> replicated by fetches (but some other tags are).

> Well, you wouldn't want to go through the trouble of writing a
> tag-message for a temporary tag, but signing and writing a short note
> for a tag that you intend those who share your workload to have is not
> that much of a bother imo.

It's not obvious from the git-tag documentation that signing makes a
difference down the road in terms of replication.  IOW, I don't
question the distinction per se, but it's counter-intuitive if you
aren't told about it.

  reply	other threads:[~2006-03-20 20:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 18:44 Pulling tags from git.git David Ho
2006-03-06 18:54 ` David Ho
2006-03-07  9:29   ` Andreas Ericsson
2006-03-07 10:33     ` Junio C Hamano
2006-03-07 12:20       ` Andreas Ericsson
2006-03-07 14:37         ` A Large Angry SCM
2006-03-07 15:35           ` Andreas Ericsson
2006-03-07 18:10             ` Junio C Hamano
2006-03-08  4:32             ` A Large Angry SCM
2006-03-08 10:13               ` Andreas Ericsson
2006-03-09  7:37         ` Florian Weimer
2006-03-09 17:24           ` Andreas Ericsson
2006-03-20 18:30             ` Florian Weimer [this message]
2006-03-20 20:31               ` Junio C Hamano
2006-03-07 16:12     ` David Ho

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=87lkv5ynnp.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=ae@op5.se \
    --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).