From: Ingo Molnar <mingo@elte.hu>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: "Jeff King" <peff@peff.net>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"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 16:27:57 +0200 [thread overview]
Message-ID: <20110608142757.GG30752@elte.hu> (raw)
In-Reply-To: <BANLkTiku_qvn73cUDBT=OxY-3jR3raoOhg@mail.gmail.com>
* Sverre Rabbelier <srabbelier@gmail.com> wrote:
> Heya,
>
> [+Peff, Duy, who seemed interested in this]
>
> On Wed, Jun 8, 2011 at 14:52, Ingo Molnar <mingo@elte.hu> wrote:
> > So it would be nice to have more separation for remotes - right now
> > they do not sit still in their sandboxes! :-)
>
> Sounds like the "tags should go in their own namespaces in git 1.8.0"
> [0] discussion? :)
>
> [0] http://thread.gmane.org/gmane.comp.version-control.git/165799/focus=165837
Cool, i like banging on open doors! :-)
Thanks,
Ingo
next prev parent reply other threads:[~2011-06-08 14:28 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 [this message]
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
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=20110608142757.GG30752@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sfr@canb.auug.org.au \
--cc=srabbelier@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.