From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ingo Molnar <mingo@elte.hu>,
git@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Q: how can i find the upstream merge point of a commit?
Date: Wed, 08 Jun 2011 13:51:07 +0200 [thread overview]
Message-ID: <1307533867.2497.997.camel@laptop> (raw)
In-Reply-To: <20110608212910.093ba753.sfr@canb.auug.org.au>
On Wed, 2011-06-08 at 21:29 +1000, Stephen Rothwell wrote:
> Hi Peter,
>
> On Wed, 08 Jun 2011 12:40:36 +0200 Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> >
> > *groan*, I tried that, but got:
> >
> > # git describe --contains 189d3c4a94ef19fca2a71a6a336e9fda900e25e7 --match '^v.*'
> ^
> These are globs. not regexps.
Yeah, figured as much, never would have thought of trying that though.
The man page said pattern, my brain made regex.
next prev parent reply other threads:[~2011-06-08 11:47 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 [this message]
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
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=1307533867.2497.997.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.