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: Thu, 22 Apr 2010 15:52:16 -0400 [thread overview]
Message-ID: <m2r3abd05a91004221252u497174bfi8a49215ad496295d@mail.gmail.com> (raw)
In-Reply-To: <20100422015251.GA25093@coredump.intra.peff.net>
Hello Jeff,
> Git grew out of the first type of workflow, and that has always been the
> default. Tools for helping the latter workflow have developed later.
> There was some discussion about changing the default, but it hurts
> people used to the current default, so we ended up with the config
> variable.
Thank you for the explanation. For what it's worth (probably 0) I vote
for the default to be 'tracking'.
-- aghiles
prev parent reply other threads:[~2010-04-22 19:52 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
2010-04-22 1:52 ` Jeff King
2010-04-22 19:52 ` Aghiles [this message]
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=m2r3abd05a91004221252u497174bfi8a49215ad496295d@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).