git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	git@vger.kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Q: how can i find the upstream merge point of a commit?
Date: Wed, 8 Jun 2011 17:18:19 +0200	[thread overview]
Message-ID: <20110608151819.GA11814@elte.hu> (raw)
In-Reply-To: <7vlixc2wpq.fsf@alter.siamese.dyndns.org>


* Junio C Hamano <gitster@pobox.com> wrote:

> Ingo Molnar <mingo@elte.hu> writes:
> 
> > Still it's not entirely logical that 'foreign' tags invade another 
> > branch this aggressively.
> 
> Is it a problem for "describe", or is the root of the problem that 
> git allowed you to slurp in 'foreign' tags that you do not care 
> about?

Well, if i checked out a linux-next related branch i'd expect those 
tags to go live, but if i stayed on -git i'd expect only Linus's tags 
to live.

I would not expect the linux-next tags to go away altogether - i 
added it as a remote, so i'd expect to see 'its' tags when i check it 
out.

at least that's my naive expectation from a 'remote' repository - if 
there's a better way to think about this then i'm eager to improve
:-)

Thanks,

	Ingo

      reply	other threads:[~2011-06-08 15:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  9:36 Q: how can i find the upstream merge point of a commit? Ingo Molnar
2011-06-08 10:32 ` Johannes Sixt
2011-06-08 10:34 ` Stephen Rothwell
2011-06-08 10:40   ` Peter Zijlstra
2011-06-08 11:29     ` Stephen Rothwell
2011-06-08 11:51       ` Peter Zijlstra
2011-06-08 12:52   ` Ingo Molnar
2011-06-08 13:49     ` Sverre Rabbelier
2011-06-08 14:27       ` Ingo Molnar
2011-06-08 15:23       ` Nguyen Thai Ngoc Duy
2011-06-14  9:56         ` Johan Herland
2011-06-14 17:12           ` Jeff King
2011-06-14 23:45             ` Johan Herland
2011-06-15 23:00               ` Jeff King
2011-06-15 23:53                 ` Junio C Hamano
2011-06-16  0:48                   ` Jeff King
2011-06-16 11:33                     ` Jakub Narebski
2011-06-08 15:01     ` Junio C Hamano
2011-06-08 15:18       ` Ingo Molnar [this message]

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=20110608151819.GA11814@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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).