git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Bill Lear <rael@zopyra.com>
Cc: git@vger.kernel.org
Subject: Re: Dangers of working on a tracking branch
Date: Thu, 15 Feb 2007 16:00:23 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0702151557410.1757@xanadu.home> (raw)
In-Reply-To: <17876.51013.561979.431717@lisa.zopyra.com>

On Thu, 15 Feb 2007, Bill Lear wrote:

> We are about to switch to git 1.5 from git 1.4.4.1.  I cannot remember
> if someone posted about this, but what is the danger of working on a
> tracking branch --- there are abundant cautions about doing this, but
> I can't recall and can't find the reason this is bad.

A tracking branch is supposed to be a local mirror of what is available 
remotely.  If you commit local changes to it then you break that model.

This is why with Git 1.5.0 tracking branches are in a different 
namespace by default to which you cannot commit.


Nicolas

  reply	other threads:[~2007-02-15 21:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 20:49 Dangers of working on a tracking branch Bill Lear
2007-02-15 21:00 ` Nicolas Pitre [this message]
2007-02-15 21:21   ` Bill Lear
2007-02-15 21:33     ` Bill Lear
2007-02-15 21:43       ` Jeff King
2007-02-15 21:53         ` Bill Lear
2007-02-15 21:58           ` Jeff King
2007-02-15 22:04             ` Bill Lear
2007-02-15 22:09               ` Shawn O. Pearce
2007-02-15 22:40                 ` Bill Lear
2007-02-15 22:49                   ` Shawn O. Pearce
2007-02-15 22:06             ` Jeff King
2007-02-15 22:30               ` Bill Lear
2007-02-16  2:00       ` Jakub Narebski
2007-02-16 15:13         ` Bill Lear
2007-02-16 15:21           ` Jeff King
2007-02-16 15:27             ` Bill Lear
2007-02-16 15:52               ` Jeff King
2007-02-16 16:10               ` Santi Béjar
2007-02-16 16:34           ` Nicolas Pitre
2007-02-16 16:40             ` Bill Lear
2007-02-15 22:14     ` Nicolas Pitre

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.0702151557410.1757@xanadu.home \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=rael@zopyra.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).