From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: What's in git.git (Mar 2009, #03; Fri, 06)
Date: Fri, 06 Mar 2009 01:44:17 -0800 [thread overview]
Message-ID: <7vab7zt28e.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vocwft5tx.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Fri, 06 Mar 2009 00:26:34 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Quite a many topics that have been scheduled for 'master' for some time
> have all graduated. With this pace we may be able to have a very short
> cycle for a change before 1.6.3 final ;-).
People who have been following the 'next' branch during 1.6.2 rc period
may already know these, but here is how the tip of 'master' looks like as
of tonight (an excerpt from the draft release notes to 1.6.3).
Updates since v1.6.2 so far
---------------------------
(usability, bells and whistles)
* "--pretty=<style>" option to the log family of commands can now be
spelled as "--format=<style>". In addition, --format=%formatstring
is a short-hand for --pretty=tformat:%formatstring.
* "--oneline" is a synonym for "--pretty=oneline --abbrev=commit".
* If you realize that you botched the patch when you are editing hunks
with the 'edit' action in git-add -i/-p, you can abort the editor to
tell git not to apply it.
* git-archive learned --output=<file> option.
* git-bisect shows not just the number of remaining commits whose goodness
is unknown, but also shows the estimated number of remaining rounds.
* git-branch -r shows HEAD symref that points at a remote branch in
interest of each tracked remote repository.
* git-config learned -e option to open an editor to edit the config file
directly.
* git-format-patch can be told to use attachment with a new configuration,
format.attach.
* git-imap-send learned to work around Thunderbird's inability to easily
disable format=flowed with a new configuration, imap.preformattedHTML.
* git-rebase can be told to rebase the series even if your branch is a
descendant of the commit you are rebasing onto with --force-rebase
option.
* git-send-email learned --confirm option to review the Cc: list before
sending the messages out.
(developers)
* Test scripts can be run under valgrind.
Fixes since v1.6.2 so far
-------------------------
All of the fixes in v1.6.2.X maintenance series are included in this
release, unless otherwise noted.
Here are fixes that this release has, but have not been backported to
v1.6.2.X series.
* .gitignore learned to handle backslash as a quoting mechanism for
comment introduction character "#" (backport by merging dd482ee if
needed).
* timestamp output in --date=relative mode used to display timestamps that
are long time ago in the default mode; it now uses "N years M months
ago", and "N years ago" (backport by picking 10edf37 if needed).
* git-add -i/-p now works with non-ASCII pathnames (backport by picking
8851f48 if needed).
* "git hash-object -w" did not read from the configuration file from the
correct .git directory (backport by merging 272459a if needed).
* git-send-email learned to correctly handle multiple Cc: addresses
(backport by merging afe756c if needed).
prev parent reply other threads:[~2009-03-06 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 8:26 What's in git.git (Mar 2009, #03; Fri, 06) Junio C Hamano
2009-03-06 9:44 ` Junio C Hamano [this message]
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=7vab7zt28e.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--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;
as well as URLs for NNTP newsgroup(s).