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

Re: [PATCH v2] git-p4: add P4 jobs to git commit message

From
Jan Durovec <jan.durovec@gmail.com>
Date
Apr 19, 2016, 21:25 UTC
Message-ID
<CABEqOBx4vCUpYTGYM9VF6QHxGGgQSG5APSHymtbV7uVxAbU+ow@mail.gmail.com>
In-Reply-To
<xmqqd1plz4p5.fsf@gitster.mtv.corp.google.com>

There's a comment on PR itself (in addition to individual commits) so theoretically it could.

It seems that for [PATCH ... n/m] e-mails the commit messages are used, so there's no reason why the PR comment couldn't be used for a cover letter.

In this case the PR comment was the same as for one of the commits. Maybe submitGit tried to be smart there? Or maybe it just really doesn't support it (yet?).

On Tue, Apr 19, 2016 at 11:09 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 20 quoted lines
> Jan Durovec <jan.durovec@gmail.com> writes:
>
>> On Tue, Apr 19, 2016 at 8:50 PM, Jan Durovec <jan.durovec@gmail.com> wrote:
>>>> Any submitGit users?  I think it lets you throw multiple-patch
>>>> series just fine.  In this case, you'd prepare a two patch series on
>>>> a branch, 1/2 being the clean-up and 2/2 being the new feature, and
>>>> if you give that branch to submitGit as a whole it should do the
>>>> right thing, I'd imagine.
>>>
>>> Hm... I'll see what it does with a pull request that has 2 commits.
>>
>> Huh... seems that it works :)
>>
>> v3 sent in 2 parts
>
> Thanks.
>
> For a series this small it does not matter, but anything longer it
> would be easier to review with a cover letter (i.e. [PATCH 0/N]).  I
> do not know if submitGit lets us do that, though.
Previous: Junio C HamanoNext: Junio C Hamano
Message 12 of 21 in “git-p4: add P4 jobs to git commit message”
  1. git-p4: add P4 jobs to git commit messageJan Durovec, Apr 16, 2016
  2. Junio C HamanoApr 19, 2016
  3. Luke DiamandApr 19, 2016
  4. Junio C HamanoApr 19, 2016
  5. Jan DurovecApr 19, 2016
  6. Junio C HamanoApr 19, 2016
  7. Jan DurovecApr 19, 2016
  8. Junio C HamanoApr 19, 2016
  9. Jan DurovecApr 19, 2016
  10. Jan DurovecApr 19, 2016
  11. Junio C HamanoApr 19, 2016
  12. Jan DurovecApr 19, 2016
  13. Junio C HamanoApr 19, 2016
  14. Jan DurovecApr 19, 2016
  15. Luke DiamandApr 20, 2016
  16. Luke DiamandApr 20, 2016
  17. Junio C HamanoApr 20, 2016
  18. Luke DiamandApr 21, 2016
  19. Jan DurovecApr 20, 2016
  20. Junio C HamanoApr 19, 2016
  21. Lars SchneiderApr 19, 2016

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.