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

Re: [PATCH] blame: can specify shas of commits to ignore on command line

From
Junio C Hamano <gitster@pobox.com>
Date
May 4, 2010, 23:01 UTC
Message-ID
<7vtyqnl19w.fsf@alter.siamese.dyndns.org>
In-Reply-To
<j2sfd211a421005041446ub9c2247ai484c2473df856b31@mail.gmail.com>
Dylan Reid <dgreid@gmail.com> writes:
> A null commit could work.  I think the behavior should be to not
> ignore the commit. Meaning if you specify a commit that introduced a
> line of code that line of code will still be blamed on the ignored
> commit.  Does That sound logical or is it too confusing?

I am already confused. If the command must return C when you say "ignore C" and C introduced a line you are interested in, then what is the point of specifying commits to be ignored?

Previous: Dylan ReidNext: Dylan Reid
Message 4 of 8 in “blame: can specify shas of commits to ignore on command line”
  1. blame: can specify shas of commits to ignore on command lineDylan Reid, May 4, 2010
  2. René ScharfeMay 4, 2010
  3. Dylan ReidMay 4, 2010
  4. Junio C HamanoMay 4, 2010
  5. Dylan ReidMay 4, 2010
  6. Junio C HamanoMay 5, 2010
  7. Dylan ReidMay 5, 2010
  8. cnighswongerMar 8, 2012

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.