From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: git@vger.kernel.org, gitster@pobox.com
Subject: [RFC/PATCH] git-branch: default to --track
Date: Fri, 6 Jul 2007 22:54:09 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707062252390.4093@racer.site> (raw)
"git branch --track" will setup config variables when branching from
a remote branch, so that if you say "git pull" while being on that
branch, it automatically fetches the correct remote, and merges the
correct branch.
Often people complain that this is not the default for "git branch".
Make it so.
Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
---
With 1.5.3 knocking at the door, maybe it is too late to include
this. However, I am in favour of changing the default behaviour
here.
builtin-branch.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/builtin-branch.c b/builtin-branch.c
index ae450b0..507b47c 100644
--- a/builtin-branch.c
+++ b/builtin-branch.c
@@ -22,7 +22,7 @@ static const char builtin_branch_usage[] =
static const char *head;
static unsigned char head_sha1[20];
-static int branch_track_remotes;
+static int branch_track_remotes = 1;
static int branch_use_color;
static char branch_colors[][COLOR_MAXLEN] = {
next reply other threads:[~2007-07-06 22:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 21:54 Johannes Schindelin [this message]
2007-07-08 8:59 ` [RFC/PATCH] git-branch: default to --track Junio C Hamano
2007-07-08 12:41 ` [PATCH] branch.autosetupmerge: allow boolean values, or "all" Johannes Schindelin
2007-07-08 18:41 ` Junio C Hamano
2007-07-08 19:15 ` Johannes Schindelin
2007-07-09 1:59 ` Paolo Bonzini
2007-07-09 2:27 ` Junio C Hamano
2007-07-09 11:35 ` [PATCH] branch --track: code cleanup and saner handling of local branches Johannes Schindelin
2007-07-09 21:05 ` Junio C Hamano
2007-07-09 21:05 ` Johannes Schindelin
2007-07-09 22:01 ` Junio C Hamano
2007-07-10 3:02 ` [PATCH 1/2] Add for_each_remote() function, and extend remote_find_tracking() Johannes Schindelin
2007-07-10 3:55 ` Daniel Barkalow
2007-07-10 14:11 ` Johannes Schindelin
2007-07-10 5:07 ` Junio C Hamano
2007-07-10 5:23 ` Daniel Barkalow
2007-07-10 17:48 ` [PATCH v2 " Johannes Schindelin
2007-07-10 18:38 ` Junio C Hamano
2007-07-10 19:28 ` Johannes Schindelin
2007-07-10 21:09 ` Daniel Barkalow
2007-07-10 17:50 ` [PATCH v2 2/2] branch --track: code cleanup and saner handling of local branches Johannes Schindelin
2007-07-10 3:05 ` [PATCH " Johannes Schindelin
2007-07-09 11:28 ` [PATCH] branch.autosetupmerge: allow boolean values, or "all" Johannes Schindelin
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=Pine.LNX.4.64.0707062252390.4093@racer.site \
--to=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).