Note that there are some explanatory texts on larger screens.

plurals
  1. POgit send-email to not alter commit dates from git format-patch
    primarykey
    data
    text
    <p><strong>Question:</strong> Is there a way to tell <code>git send-email</code> to honor <code>git format-patch</code> dates? Better still, is there way to not regard the mail date and commit date as distinct?</p> <p><strong>Observations:</strong> this is my observation about treating dates for which I have not found way to alter</p> <ol> <li>Patches created with <code>git format-patch</code> have the commit date recorded as <code>Date:</code> header.</li> <li>When using <code>git send-email</code> to send the patches, the commit date is changed to the moment of sending</li> <li>When applying the commits with <code>git am</code>, the date as in <code>Date:</code> header of the received email is used.</li> </ol> <p><strong>Partial work-around:</strong> By using a wrapper script for <code>git send-email</code>, it is possible to extract the commit date from the patch and use <code>faketime</code> or similar method to force the <code>git send-email</code> to obey the commit date. This brings two problems, however:</p> <ol> <li>Because the mail date and commit date are collapsed to one (which I regard as conceptual defect), the mail will appear in the inbox in wrong time which is inconvenient.</li> <li>I can only easily apply this method to sending one patch, not a series of patches, if I want them to appear in the same mail thread. Okay, of course I can enable SMTP debugging (<code>git send-email --smtp-debug=1</code>) and extract the <code>Message-Id</code> from the output. But then it start to look like I need to start rewriting the threading options that are already implemented in <code>git send-email</code>...</li> </ol> <p>Note that if <code>git send-email</code> would honor the commit dates recorded by <code>git format-patch</code> then I could use cover letter (<code>git send-email --cover-letter</code>) to deal with the problem number 1, relying on the threading support of the <code>git send-email</code> and MUAs.</p> <p><strong>Bonus Question:</strong> I really would like to see the original commit (implementation) dates in the applied patches for record (series of patches merged in one commit would tell the time of incorporating to the published branch). Is my thinking somehow misguided in wanting this? <em>Is there some deeper thinking in treating the email date and commit date as one?</em> This to me is analogous to pushing local changes to some public branch - the dates are kept.</p> <p><strong>P.S.</strong> There is no tags <code>git-send-email</code> and <code>git-format-patch</code> which I would like to use (reputation will not allow creating them).</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload