git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Adam" <thomas.adam22@gmail.com>
To: "Steve Hoelzer" <shoelzer@gmail.com>,
	"Thomas Adam" <thomas.adam22@gmail.com>,
	"git mailing list" <git@vger.kernel.org>
Subject: Re: How can I specify multiple refs on one line in the config file?
Date: Wed, 7 May 2008 23:38:09 +0100	[thread overview]
Message-ID: <18071eea0805071538w1e898ebalf4166b08fe7cfac3@mail.gmail.com> (raw)
In-Reply-To: <20080507222751.GC23672@genesis.frugalware.org>

2008/5/7 Miklos Vajna <vmiklos@frugalware.org>:
>
> On Wed, May 07, 2008 at 05:19:30PM -0500, Steve Hoelzer <shoelzer@gmail.com> wrote:
>  > On Wed, May 7, 2008 at 4:33 PM, Thomas Adam <thomas.adam22@gmail.com> wrote:
>  > > I might be misunderstanding you, but to push tags, there's:
>  > >
>  > > git push --tags
>  >
>  > True, but I only want to type "git push". No, it's not _really_
>  > necessary, but I'd like to set it up that way so I don't have to
>  > depend on my coworkers (new git users) remembering "--tags".
>
>  are you sure pushing tags by default is a good idea? people regularly
>  create local tags to mark a commit before a rebase, to mark a commit as
>  a fix for a given bug, etc. those tags aren't interesting for others.
>  tags which should be pushed usually rare. then you can use git push
>  origin tag v1.0, since you know which tag you really want to push.

Probably not, which is why '--tags' exists in the first place.  But
then if you're working from a shared repository (which I am -- as are
many, no doubt in a corporate environment) it's rather useful.  I
would find local tags though to be odd.

-- Thomas Adam

  reply	other threads:[~2008-05-07 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 21:15 How can I specify multiple refs on one line in the config file? Steve Hoelzer
2008-05-07 21:33 ` Thomas Adam
2008-05-07 22:19   ` Steve Hoelzer
2008-05-07 22:27     ` Miklos Vajna
2008-05-07 22:38       ` Thomas Adam [this message]
2008-05-07 23:58         ` Steve Hoelzer
2008-05-07 22:28 ` Jeff King
2008-05-07 22:29   ` Jeff King
2008-05-08  3:32     ` Jeff King

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=18071eea0805071538w1e898ebalf4166b08fe7cfac3@mail.gmail.com \
    --to=thomas.adam22@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=shoelzer@gmail.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).