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

Re: [PATCH 0/3] some documentation changes from the beginning of the alphabet

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 19, 2018, 22:49 UTC
Message-ID
<xmqqzhwd2jcq.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20180919201231.609-1-frederik@ofb.net>
Frederick Eaton <frederik@ofb.net> writes:
> I've never sent patches using git before so I thought it would be
> useful to make a small test.
... eh, welcome ;-)
Show 6 quoted lines
> I read ./Documentation/SubmittingPatches and I sent these to myself
> and practiced applying them using `git am`, and I also compiled and
> checked the revised manual pages to see that they format correctly.
> Unfortunately it was too late to run 'git diff --check' because I had
> already committed the changes to my repo, but I don't see any
> whitespace highlighted when I run 'git log -p'.
Thanks for being diligent.
Show 10 quoted lines
> By the way for some reason git-contacts shows more names when I run it
> on the patch hash than when I give it the patch name:
>
> $ ./contrib/contacts/git-contacts 222580cb60ee64f7b81fed64ec8fbfc81952557f
> Sébastien Guimmara <sebastien.guimmara@gmail.com>
> Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
> Eric Sunshine <sunshine@sunshineco.com>
> Junio C Hamano <gitster@pobox.com>
> $ ./contrib/contacts/git-contacts ./outgoing/0002-git-column.1-clarify-initial-description-provide-exa.patch                                
> Junio C Hamano <gitster@pobox.com>

I've never trusted what git-contacts say, but the latter one certainly looks strange, as

	git log --no-merges Documentation/git-column.txt

makes it clear that I have nothing to do with it ;-). Perhaps the tool gives too much credit for Signed-off-by: footer, or something.

Previous: frederik@ofb.netNext: Eric Sunshine
Message 13 of 15 in “some documentation changes from the beginning of the alphabet”
  1. 0/3 some documentation changes from the beginning of the alphabetFrederick Eaton, Sep 19, 2018
  2. 1/3 git-archimport.1: specify what kind of Arch we're talking aboutFrederick Eaton, Sep 19, 2018
  3. Junio C HamanoSep 19, 2018
  4. frederik@ofb.netSep 19, 2018
  5. 3/3 git-describe.1: clarify that "human readable" is also git-readableFrederick Eaton, Sep 19, 2018
  6. 2/3 git-column.1: clarify initial description, provide examplesFrederick Eaton, Sep 19, 2018
  7. Junio C HamanoSep 19, 2018
  8. Duy NguyenSep 20, 2018
  9. frederik@ofb.netSep 20, 2018
  10. Eric SunshineSep 21, 2018
  11. Junio C HamanoSep 21, 2018
  12. frederik@ofb.netSep 21, 2018
  13. Junio C HamanoSep 19, 2018
  14. Eric SunshineSep 21, 2018
  15. frederik@ofb.netSep 21, 2018

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.