From: lennart spitzner <lsp@informatik.uni-kiel.de>
To: git@vger.kernel.org
Subject: appropriate mailing list for gitk patches
Date: Thu, 13 Nov 2014 22:10:00 +0100 [thread overview]
Message-ID: <54651E28.9090100@informatik.uni-kiel.de> (raw)
Hello folks,
I have a patch for gitk. Should i send it to this list, or is there some
other? git/Documentation/SubmittingPatches mentions
git://ozlabs.org/~paulus/gitk (the master of which i based my commit
on), but never mentions any list(s) by name (only "the Git mailing
list", which i presume is this one).
Also, a minor question regarding patches: I wondered why patches do not
mention the commit id that the patch(es) are based on. My current guess
is that the diffs containing the sha1's is considered sufficient. Is
this the case? Are there more/other aspects?
Lennart
next reply other threads:[~2014-11-13 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 21:10 lennart spitzner [this message]
2014-11-13 21:32 ` appropriate mailing list for gitk patches Junio C Hamano
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=54651E28.9090100@informatik.uni-kiel.de \
--to=lsp@informatik.uni-kiel.de \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).