From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] Make local branches behave like remote branches when --tracked
Date: Thu, 26 Mar 2009 21:53:23 +0100 [thread overview]
Message-ID: <1238100805-19619-1-git-send-email-git@drmicha.warpmail.net> (raw)
In-Reply-To: <alpine.LNX.1.00.0903201358440.19665@iabervon.org>
[Sorry it took so long to finish... This is from my "sick bed", I hope
it doesn't show ;)]
This mini series makes local branches behave the same as remote ones
when they are used as --tracked branches. This means differences are
reported by git status and git checkout, and also that the soon to be
released tracking branch short cut (aka BEL) will work.
Michael J Gruber (2):
Test for local branches being followed with --track
Make local branches behave like remote branches when --tracked
remote.c | 9 +++++----
t/t6040-tracking-info.sh | 10 +++++++++-
2 files changed, 14 insertions(+), 5 deletions(-)
next prev parent reply other threads:[~2009-03-26 20:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 14:22 Tracking of local branches Michael J Gruber
2009-03-20 16:13 ` Michael J Gruber
2009-03-20 16:46 ` Junio C Hamano
2009-03-20 18:10 ` Daniel Barkalow
2009-03-26 20:53 ` Michael J Gruber [this message]
2009-03-26 20:53 ` [PATCH 1/2] Test for local branches being followed with --track Michael J Gruber
2009-03-26 20:53 ` [PATCH 2/2] Make local branches behave like remote branches when --tracked Michael J Gruber
2009-03-27 8:08 ` Junio C Hamano
2009-03-27 8:47 ` Michael J Gruber
2009-03-27 16:20 ` Junio C Hamano
2009-03-27 16:52 ` Michael J Gruber
2009-04-01 21:42 ` [PATCHv2 0/2] " Michael J Gruber
2009-04-01 21:42 ` [PATCHv2 1/2] Test for local branches being followed with --track Michael J Gruber
2009-04-01 21:42 ` [PATCHv2 2/2] Make local branches behave like remote branches when --tracked Michael J Gruber
2009-03-26 20:57 ` [PATCH 0/2] " Michael J Gruber
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=1238100805-19619-1-git-send-email-git@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--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).