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

Re: Avoiding uninteresting merges in Cairo

From
Shawn Pearce <spearce@spearce.org>
Date
Dec 15, 2006, 15:01 UTC
Message-ID
<20061215150130.GB17860@spearce.org>
In-Reply-To
<eluasq$v7q$3@sea.gmane.org>
Jakub Narebski <jnareb@gmail.com> wrote:
Show 12 quoted lines
> Carl Worth wrote:
> 
> > On Thu, 14 Dec 2006 22:25:30 -0500, Shawn Pearce wrote:
> 
> >>  * gitweb made it appear as though a whole lot of Carl's recent
> >>    work was somehow undone in the merge.
> > 
> > That looks like a simple gitweb bug. None of the other tools, (gitk,
> > git log -p), consider a trivial merge commit like this as having
> > anything interesting in it worth displaying.
> 
> It's not a bug, it is rather lack of feature (or misfeature).
Its a bug.

I'm not a gitweb user (meaning I almost never look at something in gitweb). But I'm clearly also not a Git newbie. ;-)

I could not fathom why that merge commit was being displayed that
way in gitweb.  I had to clone the cairo project just so I could
actually look at the commit with log/show/whatchanged/diff-tree,
because I couldn't believe what I was seeing from gitweb.
 
Previous: Jakub NarebskiNext: Junio C Hamano
Message 7 of 8 in “Avoiding uninteresting merges in Cairo”
  1. Shawn PearceDec 15, 2006
  2. Carl WorthDec 15, 2006
  3. Shawn PearceDec 15, 2006
  4. Carl WorthDec 15, 2006
  5. Shawn PearceDec 15, 2006
  6. Jakub NarebskiDec 15, 2006
  7. Shawn PearceDec 15, 2006
  8. Junio C HamanoDec 15, 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.