From: Marco Roeland <marco.roeland@xs4all.nl>
To: Jon Loeliger <jdl@freescale.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: how to find outstanding patches in non-linux-2.6 repositories ?
Date: Tue, 3 Jan 2006 20:21:03 +0100 [thread overview]
Message-ID: <20060103192103.GA15002@fiberbit.xs4all.nl> (raw)
In-Reply-To: <1136315518.11946.28.camel@cashmere.sps.mot.com>
On Tuesday January 3rd 2006 Jon Loeliger wrote:
> Could someone remind me where the <ref>..<ref> syntax
> is documented, please? I went digging, but I am lame
> and couldn't find it.
It is in the documentation for git-rev-list:
In the "Description" section for git-rev-list:
A special notation <commit1>..<commit2> can be used as a short-hand for
^<commit1> <commit2>.
--
Marco Roeland
next prev parent reply other threads:[~2006-01-03 19:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 20:01 how to find outstanding patches in non-linux-2.6 repositories? Olaf Hering
2006-01-01 20:42 ` Brian Gerst
2006-01-01 21:04 ` Olaf Hering
2006-01-01 21:32 ` Johannes Schindelin
2006-01-03 19:11 ` how to find outstanding patches in non-linux-2.6 repositories ? Jon Loeliger
2006-01-03 19:21 ` Marco Roeland [this message]
2006-01-03 19:35 ` Andreas Ericsson
2006-01-04 1:26 ` Tom Prince
2006-01-03 19:41 ` Linus Torvalds
2006-01-01 23:09 ` how to find outstanding patches in non-linux-2.6 repositories? Linus Torvalds
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=20060103192103.GA15002@fiberbit.xs4all.nl \
--to=marco.roeland@xs4all.nl \
--cc=git@vger.kernel.org \
--cc=jdl@freescale.com \
/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).