From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: What's in git.git
Date: Fri, 20 Jan 2006 00:42:40 -0800 [thread overview]
Message-ID: <7vvewfz3wf.fsf@assigned-by-dhcp.cox.net> (raw)
Now 1.1.4 is out, here is a summary of what are not there but
already merged to the "master" branch (i.e. 1.2.0 material).
Build and Environment issues:
Makefile: add 'strip' target
Fix the installation location.
Allow building of RPM from interim snapshot.
Exec git programs without using PATH (Michal Ostrowski).
Disable USE_SYMLINK_HEAD by default (Pavel Roskin)
CVS:
git-cvsimport: Add -A <author-conv-file> option (Andreas).
cvsimport: ease migration from CVSROOT/users format
Pushes and Pulls:
git-push: avoid falling back on pushing "matching" refs.
git-push: fix --tags and document it.
clone: --naked option.
Add --keep option to keep downloaded packs to git-fetch (Tom Prince).
Fix generation of "humanish" part of source repo (Uwe Zeisberger)
Usability Enhancements:
git-describe: default to HEAD
Documentation: show-branch.
show-branch: make the current branch and merge commits stand out.
show-branch: --current includes the current branch.
show-branch: take default arguments from configuration file.
octopus: allow criss-cross and clarify the message when it rejects
octopus: allow manual resolve on the last round.
checkout: automerge local changes while switching branches.
checkout: merge local modifications while switching branches.
checkout: show dirty state upon switching branches.
format-patch: always --mbox and show sane Date:
----------------------------------------------------------------
These are still cooking in "pu" branch.
Build and Environment:
Makefile: do not assume lack of IPV6 means no sockaddr_storage.
fsck-objects: support platforms without d_ino in struct dirent.
DT_UNKNOWN: do not fully trust existence of DT_UNKNOWN
* These are for the latest Cygwin builds.
Documentation:
New Tutorial (J. Bruce Fields)
* Waiting for updates after the last round of comments.
Subproject:
read-tree: --prefix=<path>/ option.
write-tree: --prefix=<path>/ and --exclude=<prefix>/.
commit-tree: --bind <sha1> <path>/ option.
* Basic design has been outlined, and read-tree/write-tree
are probably safe to push out, but commit objects that
contain "bind" lines are unsafe until fsck-objects and
rev-list are updated.
Annotate:
rev-list: stop when the file disappears (Linus)
* I've only taken a cursory look at this patch.
next reply other threads:[~2006-01-20 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 8:42 Junio C Hamano [this message]
2006-04-22 0:52 Junio C Hamano
2006-04-22 11:25 ` Johannes Schindelin
2006-04-26 11:09 Junio C Hamano
2006-05-04 8:14 Junio C Hamano
2006-05-04 9:06 ` Petr Baudis
2006-05-21 19:01 Junio C Hamano
2006-05-29 6:44 Junio C Hamano
[not found] <7vpsh75lx1.fsf@assigned-by-dhcp.cox.net>
2006-06-18 1:44 ` Junio C Hamano
2006-08-28 7:19 Junio C Hamano
2006-11-25 10:12 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=7vvewfz3wf.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®