Johannes Sixt j.s...@viscovery.net writes:
Am 9/12/2013 17:24, schrieb Junio C Hamano:
Johannes Sixt j.s...@viscovery.net writes:
Am 9/12/2013 1:32, schrieb Junio C Hamano:
* jc/ref-excludes (2013-09-03) 2 commits
Thanks for a dose of sanity. I didn't look at rev-parse. I vaguely
recall
Am 9/12/2013 1:32, schrieb Junio C Hamano:
* jc/ref-excludes (2013-09-03) 2 commits
- document --exclude option
- revision: introduce --exclude=glob to tame wildcards
People often wished a way to tell git log --branches (and git
log --remotes --not --branches) to exclude some local
Johannes Sixt j.s...@viscovery.net writes:
Am 9/12/2013 1:32, schrieb Junio C Hamano:
* jc/ref-excludes (2013-09-03) 2 commits
- document --exclude option
- revision: introduce --exclude=glob to tame wildcards
People often wished a way to tell git log --branches (and git
log --remotes
Jeff King p...@peff.net writes:
This description is slightly inaccurate since the re-roll. I think it is
now:
git config did not provide a way to set or access numbers larger
than a native int on the platform; it now provides 64-bit signed
integers on all platforms.
Not a big deal,
Am 9/12/2013 17:24, schrieb Junio C Hamano:
Johannes Sixt j.s...@viscovery.net writes:
Am 9/12/2013 1:32, schrieb Junio C Hamano:
* jc/ref-excludes (2013-09-03) 2 commits
Thanks for a dose of sanity. I didn't look at rev-parse. I vaguely
recall somebody offered follow-ups (was it you?)
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'.
The second batch of topics are now in 'master'.
You can find the changes described here in the integration branches
of the repositories listed
On Wed, Sep 11, 2013 at 04:32:23PM -0700, Junio C Hamano wrote:
* jk/config-int-range-check (2013-09-09) 5 commits
(merged to 'next' on 2013-09-09 at 9ab779d)
+ git-config: always treat --int as 64-bit internally
+ config: make numeric parsing errors more clear
+ config: set errno in
7 matches
Mail list logo
