git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: how to find outstanding patches in non-linux-2.6 repositories ?

From
Tom Prince <tom.prince@ualberta.net>
Date
Jan 4, 2006, 01:26 UTC
Message-ID
<20060104012659.GA2353@socrates>
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.
Previous: Andreas EricssonNext: Linus Torvalds
Message 8 of 10 in “how to find outstanding patches in non-linux-2.6 repositories?”
  1. Olaf HeringJan 1, 2006
  2. Brian GerstJan 1, 2006
  3. Olaf HeringJan 1, 2006
  4. Johannes SchindelinJan 1, 2006
  5. Jon LoeligerJan 3, 2006
  6. Marco RoelandJan 3, 2006
  7. Andreas EricssonJan 3, 2006
  8. Tom PrinceJan 4, 2006
  9. Linus TorvaldsJan 3, 2006
  10. Linus TorvaldsJan 1, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.