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

Re: Name/documentation on git-log --full-diff is insufficient

From
Tim Henigan <tim.henigan@gmail.com>
Date
Nov 20, 2009, 14:19 UTC
Message-ID
<32c343770911200619i38009e2fy5067a301be3fc313@mail.gmail.com>
In-Reply-To
<20091120140138.GB23718@genesis.frugalware.org>
On Fri, Nov 20, 2009 at 9:01 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:
Show 10 quoted lines
> On Thu, Nov 19, 2009 at 05:26:33PM -0600, Phil Miller <mille121@illinois.edu> wrote:
>> PS: I sent in a patch for git-cvsserver a week ago, and have seen no
>> response or action on it. Is there something I should have done
>> differently?
>
> From MaintNotes:
>
> "If you sent a patch that you did not hear from anybody for three days,
> that is a very good indication that it was dropped on the floor ---
> please do not hesitate to remind me."
...also as noted in 'Documentation/SubmittingPatches':
   - Patches should be placed inline in your email rather than attached.
   - Patches should be addressed to both:
       * gitster@pobox.com
       * git@vger.kernel.org

You should also double-check your patch against the rest of the guidelines in 'SubmittingPatches', to be sure it will apply cleanly.

Previous: Miklos Vajna
Message 3 of 3 in “Name/documentation on git-log --full-diff is insufficient”
  1. Phil MillerNov 19, 2009
  2. Miklos VajnaNov 20, 2009
  3. Tim HeniganNov 20, 2009

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.