From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: [PATCH 0/9] applymbox updates and assorted trivial patches.
Date: Wed, 20 Jul 2005 16:30:29 -0700 [thread overview]
Message-ID: <7vy881dpii.fsf@assigned-by-dhcp.cox.net> (raw)
I was experimenting with applypatch and applymbox to see how it
feels like being Linus ;-) and also I saw some trivially correct
patches on the list floating unmerged during KS/OLS.
Since I rebase my repostitory to fix up the history often, I
needed a reliable way to preserve authorship information when I
export the patches via format-patch and slurp them via applymbox.
I am sending the following changes to applymbox and format-patch
first:
[PATCH] tools/applymbox: allow manual fixing and continuing after a failure.
[PATCH] git-format-patch-script and mailinfo updates.
[PATCH] format-patch: --mbox and --check.
I wrote the first one to recover from a situation where an
earlier patch failed to apply but I still had many other e-mails
in the mailbox.
The second one allows format-patch to give ability to optionally
add From: and Date: lines as the first two lines after the patch
title line. The mailinfo program has been enhanced to grok
Date: in the top part of the message body just like From: in the
message body can override the sender of the e-mail.
The third one is an extra. It lets me export patches in a
format resembling UNIX mbox, so I can concatenate the output
together and reprocess them through applymbox.
After they are accepted, I will forward these trivially correct
patches I saw on the list, using the enhanced format-patch; they
are expected to be processed with the new applymbox as a
practice; by doing this I am also ACKing these patches:
[PATCH] debian/ fixes
[PATCH] Fix a typo in git-unpack-objects documentation.
[PATCH] Cleanup: git-verify-tag-script
[PATCH] Install git-verify-tag-script
[PATCH] Support more http features: https no cert, .netrc -> auth
[PATCH] Document "curl" requirements.
next reply other threads:[~2005-07-20 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 23:30 Junio C Hamano [this message]
2005-07-21 6:19 ` [PATCH 0/9] applymbox updates and assorted trivial patches Ryan Anderson
2005-07-21 6:58 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-07-22 23:03 Junio C Hamano
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=7vy881dpii.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).