git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: Jeff King <peff@peff.net>
Cc: Mike Galbraith <efault@gmx.de>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: git remote update -> rejected
Date: Tue, 22 Apr 2008 15:41:18 +0300	[thread overview]
Message-ID: <20080422124118.GA3098@mithlond.arda.local> (raw)
In-Reply-To: <20080422111113.GB11238@sigill.intra.peff.net>

Jeff King wrote (2008-04-22 07:11 -0400):

> remote: create fetch config lines with '+'
> 
> Since git-remote always uses remote tracking branches, it
> should be safe to always force updates of those branches.
> I.e., we should generate
> 
>   fetch = +refs/heads/*:refs/remotes/$remote/*
> 
> instead of
> 
>   fetch = refs/heads/*:refs/remotes/$remote/*
> 
> This was the behavior of the perl version, which seems to
> have been lost in the C rewrite.

I agree, the "+" should be there. I see remote tracking branches as,
well, branches that track remote repository - no matter what happens
there. Local branches are under user's personal control, so if user
wants to save/keep the information of remote branches he can create
local ones out of them: git branch localcopy $remote/$branch

  parent reply	other threads:[~2008-04-22 12:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22  9:48 git remote update -> rejected Mike Galbraith
2008-04-22 10:34 ` Jeff King
2008-04-22 10:55   ` Mike Galbraith
2008-04-22 11:11     ` Jeff King
2008-04-22 11:58       ` Johannes Schindelin
2008-04-22 12:56         ` Jeff King
2008-04-22 13:03           ` Johannes Schindelin
2008-04-22 13:09             ` Jeff King
2008-04-22 13:26               ` [PATCH] builtin-remote: resurrect forced updates to tracked branches Johannes Schindelin
2008-04-22 17:00         ` git remote update -> rejected Junio C Hamano
2008-04-22 12:41       ` Teemu Likonen [this message]
2008-04-22 12:56         ` Johannes Schindelin
2008-04-22 13:01           ` Jeff King
2008-04-22 13:05             ` Johannes Schindelin
2008-04-22 13:53               ` Paolo Bonzini
2008-04-22 13:39           ` Teemu Likonen
2008-04-22 13:49             ` Johannes Schindelin
2008-04-22 14:04               ` Teemu Likonen
2008-04-22 14:10                 ` Paolo Bonzini
2008-04-22 15:08                   ` Johannes Schindelin
2008-04-22 15:26                     ` Paolo Bonzini
2008-04-22 16:23                       ` Paolo Bonzini
2008-04-22 16:42                         ` Johannes Schindelin
2008-04-22 16:50           ` Junio C Hamano
2008-04-22 17:23             ` [PATCH] remote add: disallow --master and --mirror with non-bare repositories Johannes Schindelin
2008-04-22 18:45               ` Paolo Bonzini
2008-04-22 18:46               ` [PATCH] remote add: disallow --master and --mirror with non-bare repositories (review) Paolo Bonzini
2008-04-22 22:04                 ` 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=20080422124118.GA3098@mithlond.arda.local \
    --to=tlikonen@iki.fi \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=efault@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).