git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Multiple refs from the same remote in one git fetch
Date: Mon, 14 Aug 2006 12:49:45 +0200	[thread overview]
Message-ID: <ebpket$7dt$1@sea.gmane.org> (raw)
In-Reply-To: 20060814063309.GD21963@mellanox.co.il

Michael S. Tsirkin wrote:

> Quoting r. Junio C Hamano <junkio@cox.net>:
[...]
>> I have been hesitant to claim that it does not make any sense to
>> use more than one tracking branch for the same remote branch,
>> because the only reason I might say so is because I haven't
>> thought of a good usage pattern to do so.
>> 
>> But apparently you do use more than one local branch to keep
>> track of one remote branch.  How do you use it for?  Do you feel
>> it is a good feature to be able to do that, or do you think it
>> is just a mistake and more sensible error message is what we
>> would really want?
>> 
> 
> Well, what I was *trying* to do is simply add a more descriptive name for
> the linus master branch to my existing tree.
> So it seemed like an obvious idea to add
> 
> Pull: master:origin
> Pull: master:linus_master

Couldn't you do this via symlinks or symrefs? 

BTW. Do we support symrefs other than HEAD, and does reflog works with
symref heads, and symlinked heads?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  parent reply	other threads:[~2006-08-14 10:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 14:03 [PATCH] mailinfo: accept >From in message header Michael S. Tsirkin
2006-07-27 21:22 ` Junio C Hamano
2006-07-27 21:32   ` Michael S. Tsirkin
2006-08-07 12:51 ` Multiple pulls from the same branch in .git/remotes/origin Michael S. Tsirkin
2006-08-07 18:28   ` Junio C Hamano
2006-08-07 19:38     ` Michael S. Tsirkin
2006-08-07 19:53       ` Junio C Hamano
2006-08-07 21:05         ` Michael S. Tsirkin
2006-08-07 22:04           ` Junio C Hamano
2006-08-07 22:33             ` Michael S. Tsirkin
2006-08-07 22:19         ` [PATCH] Multiple refs from the same remote in one git fetch Michael S. Tsirkin
2006-08-07 23:05           ` Junio C Hamano
2006-08-12 22:39             ` Michael S. Tsirkin
2006-08-12 23:07               ` Junio C Hamano
2006-08-14  0:13                 ` Michael S. Tsirkin
2006-08-14  0:20                   ` Junio C Hamano
2006-08-14  5:13                     ` Michael S. Tsirkin
2006-08-14  5:53                       ` Junio C Hamano
2006-08-14  6:33                         ` Michael S. Tsirkin
2006-08-14  7:34                           ` Junio C Hamano
2006-08-14  7:42                             ` Michael S. Tsirkin
2006-08-14 10:49                           ` Jakub Narebski [this message]
2006-08-14 17:51                             ` Michael S. Tsirkin
2006-08-14 18:33                               ` Jakub Narebski
2006-08-14 19:17                                 ` Michael S. Tsirkin
2006-08-22 15:10                       ` [PATCH repost] " Michael S. Tsirkin
2006-08-23  1:34                         ` Junio C Hamano

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='ebpket$7dt$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /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).