Re: What's cooking in git.git (Oct 2013, #04; Fri, 18)

2013-10-22 Thread Junio C Hamano
Jeff King p...@peff.net writes:

 On Fri, Oct 18, 2013 at 03:14:49PM -0700, Junio C Hamano wrote:

 * jn/add-2.0-u-A-sans-pathspec (2013-04-26) 1 commit
 * jc/push-2.0-default-to-simple (2013-06-18) 1 commit
 * jc/add-2.0-ignore-removal (2013-04-22) 1 commit
  ...
  Will cook in 'next' until Git 2.0.

 I notice that these are not actually in 'next', despite the
 descriptions.  Should they be, to give them wider exposure?

We have been running with their respective preparatory migration
steps in the released versions, so we are ready to do so.  These
last steps of the multi-step transition should probably cook in
'next' for a cycle or two before the final 2.0 development cycle.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: What's cooking in git.git (Oct 2013, #04; Fri, 18)

2013-10-19 Thread Jeff King
On Fri, Oct 18, 2013 at 03:14:49PM -0700, Junio C Hamano wrote:

 * jn/add-2.0-u-A-sans-pathspec (2013-04-26) 1 commit
  - git add: -u/-A now affects the entire working tree
 
  Will cook in 'next' until Git 2.0.
 
 
 * jc/core-checkstat-2.0 (2013-05-06) 1 commit
  - core.statinfo: remove as promised in Git 2.0
 
  Will cook in 'next' until Git 2.0.
 
 
 * jc/push-2.0-default-to-simple (2013-06-18) 1 commit
  - push: switch default from matching to simple
 
  Will cook in 'next' until Git 2.0.
 
 
 * jc/add-2.0-ignore-removal (2013-04-22) 1 commit
  - git add pathspec... defaults to -A
 
  Updated endgame for git add pathspec that defaults to --all
  aka --no-ignore-removal.
 
  Will cook in 'next' until Git 2.0.

I notice that these are not actually in 'next', despite the
descriptions.  Should they be, to give them wider exposure?

-Peff
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: What's cooking in git.git (Oct 2013, #04; Fri, 18)

2013-10-19 Thread Felipe Contreras
Jeff King wrote:
 On Fri, Oct 18, 2013 at 03:14:49PM -0700, Junio C Hamano wrote:
 
  * jn/add-2.0-u-A-sans-pathspec (2013-04-26) 1 commit
   - git add: -u/-A now affects the entire working tree
  
   Will cook in 'next' until Git 2.0.
  
  
  * jc/core-checkstat-2.0 (2013-05-06) 1 commit
   - core.statinfo: remove as promised in Git 2.0
  
   Will cook in 'next' until Git 2.0.
  
  
  * jc/push-2.0-default-to-simple (2013-06-18) 1 commit
   - push: switch default from matching to simple
  
   Will cook in 'next' until Git 2.0.
  
  
  * jc/add-2.0-ignore-removal (2013-04-22) 1 commit
   - git add pathspec... defaults to -A
  
   Updated endgame for git add pathspec that defaults to --all
   aka --no-ignore-removal.
  
   Will cook in 'next' until Git 2.0.
 
 I notice that these are not actually in 'next', despite the
 descriptions.  Should they be, to give them wider exposure?

I say they shouldn't be, unless the next version after 1.8 is 2.0. There should
be a separate branch for 2.0.

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


What's cooking in git.git (Oct 2013, #04; Fri, 18)

2013-10-18 Thread Junio C Hamano
Here are the topics that have been cooking.  Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'.

You can find the changes described here in the integration branches
of the repositories listed at

http://git-blame.blogspot.com/p/git-public-repositories.html

--
[Graduated to master]

* es/name-hash-no-trailing-slash-in-dirs (2013-09-17) 4 commits
  (merged to 'next' on 2013-09-20 at 9633d9a)
 + dir: revert work-around for retired dangerous behavior
 + name-hash: stop storing trailing '/' on paths in index_state.dir_hash
 + employ new explicit exists in index? API
 + name-hash: refactor polymorphic index_name_exists()

 Clean up the internal of the name-hash mechanism used to work
 around case insensitivity on some filesystems to cleanly fix a
 long-standing API glitch where the caller of cache_name_exists()
 that ask about a directory with a counted string was required to
 have '/' at one location past the end of the string.


* jc/checkout-detach-doc (2013-09-11) 1 commit
  (merged to 'next' on 2013-09-17 at 438cf13)
 + checkout: update synopsys and documentation on detaching HEAD

 git checkout [--detach] commit was listed poorly in the
 synopsis section of its documentation.


* jc/reflog-doc (2013-06-19) 1 commit
  (merged to 'next' on 2013-09-25 at 4eb0c14)
 + setup_reflog_action: document the rules for using GIT_REFLOG_ACTION

 Document rules to use GIT_REFLOG_ACTION variable in the scripted
 Porcelain.  git-rebase--interactive locally violates them, but it
 is a leaf user that does not call out to or dot-source other
 scripts, so it does not urgently need to be fixed.


* jk/clone-progress-to-stderr (2013-09-18) 3 commits
  (merged to 'next' on 2013-09-25 at 137af9e)
 + clone: always set transport options
 + clone: treat checking connectivity like other progress
 + clone: send diagnostic messages to stderr

 Some progress and diagnostic messages from git clone were
 incorrectly sent to the standard output stream, not to the standard
 error stream.


* jk/format-patch-from (2013-09-20) 1 commit
  (merged to 'next' on 2013-09-20 at 0506530)
 + format-patch: print in-body From only when needed

 format-patch --from=whom forgot to omit unnecessary in-body
 from line, i.e. when whom is the same as the real author.


* jk/trailing-slash-in-pathspec (2013-09-13) 2 commits
  (merged to 'next' on 2013-09-17 at 18fe277)
 + reset: handle submodule with trailing slash
 + rm: re-use parse_pathspec's trailing-slash removal

 Code refactoring.


* lc/filter-branch-too-many-refs (2013-09-12) 1 commit
  (merged to 'next' on 2013-09-17 at 31cd01a)
 + Allow git-filter-branch to process large repositories with lots of branches.

 git filter-branch in a repository with many refs blew limit of
 command line length.


* sb/repack-in-c (2013-09-17) 3 commits
  (merged to 'next' on 2013-09-25 at 7c47036)
 + repack: improve warnings about failure of renaming and removing files
 + repack: retain the return value of pack-objects
 + repack: rewrite the shell script in C

 Rerolled, and I think it is in a reasonably good shape.

--
[New Topics]

* mm/checkout-auto-track-fix (2013-10-18) 2 commits
 - checkout: proper error message on 'git checkout foo bar --'
 - checkout: allow dwim for branch creation for git checkout $branch --

 git checkout topic, when there is not yet a local topic branch
 but there is a unique remote-tracking branch for a remote topic
 branch, pretended as if git checkout -t -b topic remote/$r/topic
 (for that unique remote $r) was run. This hack however was not
 implemented for git checkout topic --.

 Will merge to 'next'.


* hn/log-graph-color-octopus (2013-10-18) 1 commit
 - graph: fix coloring around octopus merges

 Will merge to 'next'.


* nd/gc-lock-against-each-other (2013-10-18) 1 commit
 - gc: remove gc.pid file at end of execution

 Will merge to 'next'.

--
[Stalled]

* np/pack-v4 (2013-09-18) 90 commits
 - packv4-parse.c: add tree offset caching
 - t1050: replace one instance of show-index with verify-pack
 - index-pack, pack-objects: allow creating .idx v2 with .pack v4
 - unpack-objects: decode v4 trees
 - unpack-objects: allow to save processed bytes to a buffer
 - ...

 Nico and Duy advancing the eternal vaporware pack-v4.  This is here
 primarily for wider distribution of the preview edition.


* sc/doc-howto-dumb-http (2013-10-16) 1 commit
 . doc/howto: warn about (dumb)http server document being too old

 The new text needs to go somewhere in the body of the document,
 not before the title line.


* tr/merge-recursive-index-only (2013-07-07) 3 commits
 - merge-recursive: -Xindex-only to leave worktree unchanged
 - merge-recursive: untangle double meaning of o-call_depth
 - merge-recursive: remove dead conditional in update_stages()

 Holding until there is a caller to learn from.