git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aghiles <aghilesk@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git list <git@vger.kernel.org>
Subject: Re: git push in --tracked branches.
Date: Wed, 21 Apr 2010 21:13:14 -0400	[thread overview]
Message-ID: <i2n3abd05a91004211813t8111c77am381bc0b8226a0c9b@mail.gmail.com> (raw)
In-Reply-To: <20100422004433.GC14249@coredump.intra.peff.net>

On Wed, Apr 21, 2010, Jeff King <peff@peff.net> wrote:

> "git push" will by default push matching refs. This has been the
> behavior since day one. See the description of push.default in "git help
> config" for other options (I think you want "tracking").

Thank you very much. The 'tracking' case is what I need. Could you
enlighten me why pushing all matching branches is a sensible default ?
It seems like an unusual thing to do.

  -- aghiles

  reply	other threads:[~2010-04-22  1:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22  0:02 git push in --tracked branches Aghiles
2010-04-22  0:44 ` Jeff King
2010-04-22  1:13   ` Aghiles [this message]
2010-04-22  1:52     ` Jeff King
2010-04-22 19:52       ` Aghiles

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=i2n3abd05a91004211813t8111c77am381bc0b8226a0c9b@mail.gmail.com \
    --to=aghilesk@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).