git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Victor Engmark <victor.engmark@terreactive.ch>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Steffen Daode Nurpmeso <sdaoden@googlemail.com>, git@vger.kernel.org
Subject: Re: Jabber, question on push,pull and --tags, and no help but jabber
Date: Mon, 6 Jun 2011 17:34:05 +0200	[thread overview]
Message-ID: <20110606153405.GA15894@victor.terreactive.ch> (raw)
In-Reply-To: <9215090.63086.1307370716794.JavaMail.trustmail@mail1.terreactive.ch>

On Mon, Jun 06, 2011 at 04:31:50PM +0200, Michael J Gruber wrote:
> Steffen Daode Nurpmeso venit, vidit, dixit 06.06.2011 15:02:
> > Hello GIT,
> >     first paragraph is reserved for praising your existence.
> >     'Used cvs(1) for long years in small team projects with local
> >     private repos and never felt the need for anything else.  2011
> >     is different.  I first tried you but failed resoundingly.  Due
> >     to vim(1) and mutt(1) i discovered hg(1) and i still love it's
> >     simple usage.  'Talking about the front-end anyway.  It's huge
> >     memory consumption and slow performance forbids it's usage on
> >     our old PCs (e.g. Cyrix 166+) though.  So i came back and
> >     found you still receptive!  And the more i work, the less
> >     i hurt, the greater the knowledge, the smoother the
> >     interaction.  Are you the final word on RC in the end?
> > 
> > I stumbled over one thing i don't understand, because it seems
> > illogical: why do i need to use --tags to force pushing of tags?
> > Because there is even a config option for the latter, i suspect
> > this is because of intention.  It would be nice to get some
> > information on the background of that, like a link to yet existing
> > documentation.  Anyway i was a bit astonished to look at some
> 
> Tags may contain private information. Say you pull some changes from
> your head of group, find a strange commit you want to look at later and
> tag it with "what-is-this-crap"...

You could use the same argument about commit log messages, branch names
and code comments. No go ;)

> More seriously, tags are not part of the "remotes layout", so when you
> push them and others pull them they overwrite their tags if there's a
> name clash.

That's odd - I wouldn't expect anything handled by Git to be simply
overwritten without merging. Is there some technical reason for this, or
is it just not implemented yet?

If it makes more sense to casual users, how about simply making --tags
the default, and --no-tags optional?

Cheers
-- 
Victor
terreActive AG
Kasinostrasse 30
CH-5001 Aarau
Tel: +41 62 834 00 55
Fax: +41 62 823 93 56
www.terreactive.ch

Wir sichern Ihren Erfolg - seit 15 Jahren

  parent reply	other threads:[~2011-06-06 15:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 13:02 Jabber, question on push,pull and --tags, and no help but jabber Steffen Daode Nurpmeso
2011-06-06 14:31 ` Michael J Gruber
2011-06-06 15:21   ` Felipe Contreras
2011-06-06 21:46   ` Steffen Daode Nurpmeso
2011-06-07  5:47     ` Michael J Gruber
2011-06-07 10:24       ` Steffen Daode Nurpmeso
     [not found] ` <9215090.63086.1307370716794.JavaMail.trustmail@mail1.terreactive.ch>
2011-06-06 15:34   ` Victor Engmark [this message]
2011-06-06 17:58     ` Junio C Hamano
2011-06-07 10:48 ` [PATCH] Notes that tags need to pushed explicitely Steffen Daode Nurpmeso
2011-06-07 14:12   ` Junio C Hamano
2011-06-07 15:33     ` [PATCH] Remarks that tags need to be pushed explicitly Steffen Daode Nurpmeso
2011-06-10 20:39     ` [PATCH v2] " Steffen Daode Nurpmeso
2011-06-10 21:24       ` Junio C Hamano
2011-06-11 17:20         ` Steffen Daode Nurpmeso

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=20110606153405.GA15894@victor.terreactive.ch \
    --to=victor.engmark@terreactive.ch \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=sdaoden@googlemail.com \
    /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).