From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] git-branch: allow --track to work w/local branches
Date: Sun, 17 Feb 2008 13:05:36 -0500 [thread overview]
Message-ID: <76718490802171005xaed572dkd59ed822897fdb3a@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0802161143290.30505@racer.site>
On Feb 16, 2008 6:45 AM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> AFAIR the problem was that you were (rightfully) annoyed when you were
> setting up your local branches, and all of a sudden, they were set up with
> loads of tracking information, cluttering your config.
>
> Basically, that is the reason why we disallowed tracking information to be
> set up for local branching.
Hrmm, I was annoyed that when setting up my local branches, they *don't*
get tracking information. Otherwise I can't use "git pull" with them,
which I'd like to. So maybe something like:
* Using --track or --notrack adds (or doesn't) the information, because
well, I specified it explicitly.
* Otherwise (if neither --track nor --notrack) is specified, check the
setting of branch.autosetupmerge. Currently it's a boolean, but
perhaps it can take on a new setting and have:
- false
- true
- always ; new setting which means to setup tracking information for
; both local and remote branches
?
j.
prev parent reply other threads:[~2008-02-17 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 3:45 [RFC PATCH 1/2] git-branch: allow --track to work w/local branches Jay Soffian
2008-02-16 3:45 ` [RFC PATCH 2/2] new --rebase option to set branch.*.rebase for new branches Jay Soffian
2008-02-16 5:10 ` [RFC PATCH 1/2] git-branch: allow --track to work w/local branches Junio C Hamano
2008-02-16 7:07 ` Jay Soffian
2008-02-16 11:45 ` Johannes Schindelin
2008-02-17 18:05 ` Jay Soffian [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=76718490802171005xaed572dkd59ed822897fdb3a@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).