From: Tom Prince <tom.prince@ualberta.net>
To: git@vger.kernel.org
Subject: Re: how to find outstanding patches in non-linux-2.6 repositories ?
Date: Tue, 03 Jan 2006 18:26:59 -0700 [thread overview]
Message-ID: <20060104012659.GA2353@socrates> (raw)
In-Reply-To: <43BAD1F2.8040209@op5.se>
On Tue, Jan 03, 2006 at 08:35:14PM +0100, Andreas Ericsson wrote:
> "origin..HEAD" is a valid and fairly common range.
> "HEAD..origin" is not (well, it is, but it doesn't include any commits
> since it's going backwards).
>
It depends on what you are doing. When I update my git repository, I do
git fetch
git-whatchanged master..origin
git pull
to find out what changed since I last updated.
next prev parent reply other threads:[~2006-01-04 1:27 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
2006-01-03 19:35 ` Andreas Ericsson
2006-01-04 1:26 ` Tom Prince [this message]
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=20060104012659.GA2353@socrates \
--to=tom.prince@ualberta.net \
--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 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.