Git development
 help / color / mirror / Atom feed
From: Tim Henigan <tim.henigan@gmail.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Phil Miller <mille121@illinois.edu>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Name/documentation on git-log --full-diff is insufficient
Date: Fri, 20 Nov 2009 09:19:00 -0500	[thread overview]
Message-ID: <32c343770911200619i38009e2fy5067a301be3fc313@mail.gmail.com> (raw)
In-Reply-To: <20091120140138.GB23718@genesis.frugalware.org>

On Fri, Nov 20, 2009 at 9:01 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> 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.

      reply	other threads:[~2009-11-20 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19 23:26 Name/documentation on git-log --full-diff is insufficient Phil Miller
2009-11-20 14:01 ` Miklos Vajna
2009-11-20 14:19   ` Tim Henigan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32c343770911200619i38009e2fy5067a301be3fc313@mail.gmail.com \
    --to=tim.henigan@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mille121@illinois.edu \
    --cc=vmiklos@frugalware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox