From: Jeff King <peff@peff.net> To: Derrick Stolee <stolee@gmail.com> Cc: "Elijah Newren" <newren@gmail.com>, "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>, "Git Mailing List" <git@vger.kernel.org>, "Derrick Stolee" <dstolee@microsoft.com>, "Jonathan Tan" <jonathantanmy@google.com>, "Taylor Blau" <me@ttaylorr.com>, "René Scharfe" <l.s.r@web.de> Subject: Re: [PATCH v3 0/4] Optimization batch 12: miscellaneous unthemed stuff Date: Fri, 4 Jun 2021 15:53:00 -0400 [thread overview] Message-ID: <YLqEnEJgQANm1SCD@coredump.intra.peff.net> (raw) In-Reply-To: <c9d596f3-cfc9-4bb7-1008-4873dafd8270@gmail.com> On Fri, Jun 04, 2021 at 02:42:03PM -0400, Derrick Stolee wrote: > > Whether "Acked-by" happens after the author signs off or not is > > debatable. Obviously it happens after the version of the patch that is > > sent out. But if you re-send with an Acked-by, is the signoff your one > > from before that happened first, or a new one that happened as you sent > > out the patch? Perhaps a question for the philosophers. ;) > > I guess I was just interpreting that the "Acked-by" was part of > the content you created, and hence it should be covered by the > sign-off. I can imagine that if Junio added it, then it would be > after your sign-off but before his. FWIW, that's how I interpret it, too. I was curious how it looks for my own patches, which is easy-ish to dig up with: git log --author=peff --grep=Acked-by --format='%H%n%(trailers)' They're mostly after my signoff there, but I think that's because I very rarely add in the Ack, and mostly Junio does it (likewise for Reviewed-by). My workflow is maybe a little different than others, too, in that I very rarely signoff patches in my repo, but add it via "format-patch -s" when sending them out (so naturally it would come after anything I had typed). > > Anyway, I think it is perfectly fine either way (as your numbers > > indicate). > > I agree. I didn't mean to make a big deal of it. It was a little bit of an interesting diversion, though. :) -Peff
next prev parent reply other threads:[~2021-06-04 19:53 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-27 8:37 [PATCH 0/5] " Elijah Newren via GitGitGadget 2021-05-27 8:37 ` [PATCH 1/5] merge-ort: replace string_list_df_name_compare with faster alternative Elijah Newren via GitGitGadget 2021-05-27 21:00 ` René Scharfe 2021-05-27 22:47 ` Elijah Newren 2021-05-28 16:12 ` René Scharfe 2021-05-28 18:09 ` Elijah Newren 2021-05-28 1:32 ` Taylor Blau 2021-05-28 4:10 ` Elijah Newren 2021-05-27 8:37 ` [PATCH 2/5] diffcore-rename: avoid unnecessary strdup'ing in break_idx Elijah Newren via GitGitGadget 2021-05-27 8:37 ` [PATCH 3/5] diffcore-rename: enable limiting rename detection to relevant destinations Elijah Newren via GitGitGadget 2021-05-27 8:37 ` [PATCH 4/5] Fix various issues found in comments Elijah Newren via GitGitGadget 2021-05-27 8:37 ` [PATCH 5/5] merge-ort: miscellaneous touch-ups Elijah Newren via GitGitGadget 2021-06-01 14:58 ` [PATCH v2 0/5] Optimization batch 12: miscellaneous unthemed stuff Elijah Newren via GitGitGadget 2021-06-01 14:58 ` [PATCH v2 1/5] merge-ort: replace string_list_df_name_compare with faster alternative Elijah Newren via GitGitGadget 2021-06-02 11:29 ` Derrick Stolee 2021-06-01 14:58 ` [PATCH v2 2/5] diffcore-rename: avoid unnecessary strdup'ing in break_idx Elijah Newren via GitGitGadget 2021-06-01 14:58 ` [PATCH v2 3/5] diffcore-rename: enable limiting rename detection to relevant destinations Elijah Newren via GitGitGadget 2021-06-03 12:54 ` Derrick Stolee 2021-06-03 14:13 ` Elijah Newren 2021-06-01 14:58 ` [PATCH v2 4/5] Fix various issues found in comments Elijah Newren via GitGitGadget 2021-06-01 14:58 ` [PATCH v2 5/5] merge-ort: miscellaneous touch-ups Elijah Newren via GitGitGadget 2021-06-03 12:55 ` [PATCH v2 0/5] Optimization batch 12: miscellaneous unthemed stuff Derrick Stolee 2021-06-04 4:39 ` [PATCH v3 0/4] " Elijah Newren via GitGitGadget 2021-06-04 4:39 ` [PATCH v3 1/4] merge-ort: replace string_list_df_name_compare with faster alternative Elijah Newren via GitGitGadget 2021-06-04 4:39 ` [PATCH v3 2/4] diffcore-rename: avoid unnecessary strdup'ing in break_idx Elijah Newren via GitGitGadget 2021-06-04 4:39 ` [PATCH v3 3/4] Fix various issues found in comments Elijah Newren via GitGitGadget 2021-06-04 4:39 ` [PATCH v3 4/4] merge-ort: miscellaneous touch-ups Elijah Newren via GitGitGadget 2021-06-04 13:11 ` [PATCH v3 0/4] Optimization batch 12: miscellaneous unthemed stuff Derrick Stolee 2021-06-04 15:48 ` Elijah Newren 2021-06-04 16:30 ` Elijah Newren 2021-06-04 16:35 ` Jeff King 2021-06-04 18:42 ` Derrick Stolee 2021-06-04 19:43 ` Elijah Newren 2021-06-04 19:53 ` Jeff King [this message] 2021-06-08 16:11 ` [PATCH v4 " Elijah Newren via GitGitGadget 2021-06-08 16:11 ` [PATCH v4 1/4] merge-ort: replace string_list_df_name_compare with faster alternative Elijah Newren via GitGitGadget 2021-06-08 16:11 ` [PATCH v4 2/4] diffcore-rename: avoid unnecessary strdup'ing in break_idx Elijah Newren via GitGitGadget 2021-06-08 16:11 ` [PATCH v4 3/4] Fix various issues found in comments Elijah Newren via GitGitGadget 2021-06-08 16:11 ` [PATCH v4 4/4] merge-ort: miscellaneous touch-ups Elijah Newren via GitGitGadget
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=YLqEnEJgQANm1SCD@coredump.intra.peff.net \ --to=peff@peff.net \ --cc=dstolee@microsoft.com \ --cc=git@vger.kernel.org \ --cc=gitgitgadget@gmail.com \ --cc=jonathantanmy@google.com \ --cc=l.s.r@web.de \ --cc=me@ttaylorr.com \ --cc=newren@gmail.com \ --cc=stolee@gmail.com \ --subject='Re: [PATCH v3 0/4] Optimization batch 12: miscellaneous unthemed stuff' \ /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
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.