Short term release plans

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

 



"Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes:

> Be nice to get them into your next release, whatever that winds
> up being.  ;-)

Surely git-gui 0.6.3 will be in 1.5.0.4, but I'd like to start
planning for 1.5.1 now.

In addition to what are described in the current 1.5.1 draft
release notes, I'd like to have a few topics graduated to
'master' and declare 1.5.1 by the end of the month.

That would mean we would have these biggies among other things
in 1.5.1:

Already in 'master':

 - git-apply subdirectory behaviour fix
 - git-remote update
 - git-bundle
 - working on filesystems without symbolic links
 - automatic CRLF munging
 - git-rev-list --boundary --max-count (broken)
 - /etc/gitconfig

Cooking in 'next':

 - git-diff --no-index
 - built-in git-revert/git-cherry-pick
 - git-rev-list --boundary --max-count fix (this is sorely
   needed to make "gitk -50 master" to work)
 - handling corrupt loose objects in git-fsck and unpack_sha1_file
 - commit --interactive
 - format-patch --inline/--attach

Not in 'next' yet, but would like to have in 1.5.1:

 - git-branch --track and git-checkout -B

In 'next' or 'pu' but needs more work, will not be in 1.5.1:

 - git-fetch half-C-rewrite.
 - .gitattributes (the code needs redesign --- handling multiple
   actions on a single path is nasty).
 - git-merge-subtree (subtree matching needs more work).


-
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]