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

Re: [PATCH] Stop git-rev-list at sha1 match

From
Petr Baudis <pasky@ucw.cz>
Date
May 11, 2005, 22:50 UTC
Message-ID
<20050511225058.GK22686@pasky.ji.cz>
In-Reply-To
<1115851742.22180.154.camel@tglx>

Dear diary, on Thu, May 12, 2005 at 12:49:02AM CEST, I got a letter where Thomas Gleixner <tglx@linutronix.de> told me that...

Show 14 quoted lines
> Rn   o
>      | \
> Rn-1 o  |
>      |  o Mn
>      |  o Mn-1
> Rn-2 o /
> Rn-3 o
> 
> If you are in Repository R, then tracking Rn to Rn-123 gives you a
> linear result depending on the stop point you chose.
> Rn
> ---- Stop = Rn-1
> Rn-1
> ---- Stop = Rn-2

Mn Mn-1

> Rn-2
> ---- Stop = Rn-3
> 
> The diff between Rn and Rn-1 contains always the changes merged from M

Yes, but you get the merge commits again since rev-list follows all the parents.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
Previous: Thomas GleixnerNext: Thomas Gleixner
Message 7 of 13 in “Stop git-rev-list at sha1 match”
  1. Stop git-rev-list at sha1 matchThomas Gleixner, May 11, 2005
  2. Junio C HamanoMay 11, 2005
  3. Thomas GleixnerMay 11, 2005
  4. Junio C HamanoMay 11, 2005
  5. Petr BaudisMay 11, 2005
  6. Thomas GleixnerMay 11, 2005
  7. Petr BaudisMay 11, 2005
  8. Thomas GleixnerMay 11, 2005
  9. Petr BaudisMay 11, 2005
  10. Thomas GleixnerMay 12, 2005
  11. Petr BaudisMay 13, 2005
  12. Junio C HamanoMay 12, 2005
  13. Junio C HamanoMay 12, 2005

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.