Re: [PATCH] rebase -i: fixup fixup! fixup!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andrew Pimlott <andrew@xxxxxxxxxxx> writes:

Just reponding for the "procedual" part for now.

> So if I don't want to break the discussion, should I append the unedited
> format-patch output to my message after "scissors", or should I send it
> as a whole new message with --in-reply-to?  Or something else?  I'll try
> the first.

Which is fine, and you are almost there, but you do not want

 (1) "From 99023b..." that is not part of the message (it is a
     delimiter between multiple patches when/in case a file contains
     more than one);

 (2) "From: Andrew..." that is the same as the e-mail header in the
     message I am responding to;

 (3) "Date: ..." which is older than the e-mail header in the
     message I am responding to---the latter is the date people
     actually saw this patch on the mailing list, so it is
     preferrable to use it than the timestamp in your repository.

So in this case, I'd expect to see, after the "-- >8 --" line, only
"Subject: " line, a blank and the log message.

>
> ---8<---
> From 99023bff23f18a341441d6b7c447d9630a11b489 Mon Sep 17 00:00:00 2001
> From: Andrew Pimlott <andrew@xxxxxxxxxxx>
> Date: Fri, 14 Jun 2013 10:33:16 -0700
> Subject: [PATCH 1/4] rebase -i: handle fixup! fixup! in --autosquash
>
> In rebase -i --autosquash, ignore all "fixup! " or "squash! " after the
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]