From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Post 1.4.0 merge status
Date: Sat, 17 Jun 2006 14:38:59 -0700 [thread overview]
Message-ID: <7virmz798s.fsf@assigned-by-dhcp.cox.net> (raw)
I thank everybody who submitted patches while I was away.
I'm trying to catch up with you and have merged the following so
far to "master". Will push them out shortly after I review them
for the last time, hopefully sometime today:
- pulled git-svn updates from Eric Wong (I first applied the
patches from the list to a test branch, and compared it with
the result of the pull onto the master -- they match, so I
decided to take the pull result).
- pulled gitk from Paul to fix "Re-read references".
- git whatchanged to show full-history from Linus.
- Portability of t4101 test for diff implementations that do
not do "\No newline..." from Dennis Stosberg.
- mailinfo fix from Eric W Biederman not to confuse "From: "
lines in the middle of log message as an in-body header.
- gitweb 'blame' that can be switched on/off from Florian
Foster.
- gitweb README update from Jakub.
- git-blame updates to add -time from Fredrik.
- three patches to cvsimport from Martin.
- strlcpy from Peter Eriksen.
- a p4import update from Sean.
- cvsexportcommit typofix from Sven Verdoolaege.
I'll be looking at these after the above;
- 2 patches to diff (color and -b/w) from Johannes.
- avoiding "make prefix=A ; make prefix=B install" confusion
from Yakov.
I've queued the following to look at in the next round;
- format-patch -s fix from Eric W Biederman;
- 7+1 patches to make am and commands required for it built-in
from Lukas.
- raw-blob output from gitweb by Jakub.
- big "SHA1"->"SHA-1" and other documentation updates from
Horst; I was hoping to merge this while flying over Pacific,
but I seemed to have duplicates and was too tired and fell
asleep.
reply other threads:[~2006-06-17 21:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7virmz798s.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.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