messages from 2018-05-23 02:35:25 to 2018-05-25 16:44:03 UTC [more...]
[PATCH 1/2] diff: turn --ita-invisible-in-index on by default
2018-05-25 16:43 UTC (4+ messages)
[PATCH v8 00/16] rebase -i: offer to recreate commit topology by rebasing merges
2018-05-25 15:44 UTC (4+ messages)
` [PATCH v9 00/17] "
[PATCH v2] checkout & worktree: introduce checkout.implicitRemote
2018-05-25 14:42 UTC (4+ messages)
` [PATCH v3] "
[PATCH] cherry-pick: do not error on non-merge commits when '-m 1' is specified
2018-05-25 12:42 UTC
What's cooking in git.git (May 2018, #03; Wed, 23)
2018-05-25 12:31 UTC (6+ messages)
` js/empty-config-section-fix, was "
What's cooking in git.git (May 2018, #02; Thu, 17)
2018-05-25 12:28 UTC (12+ messages)
` jk/branch-l-0-deprecation (was Re: What's cooking in git.git (May 2018, #02; Thu, 17))
` [PATCH] branch: issue "-l" deprecation warning after pager starts
` sb/submodule-move-nested breaks t7411 under GIT_FSMONITOR_TEST
[PATCH v2] t: make many tests depend less on the refs being files
2018-05-25 11:22 UTC (7+ messages)
"git grep" and "working tree" vs "working directory"
2018-05-25 10:56 UTC (4+ messages)
[PATCH] completion: complete remote names too
2018-05-25 10:48 UTC
[GSoC][PATCH v2 0/4] rebase: split rebase -p from rebase -i
2018-05-25 9:51 UTC (8+ messages)
` [GSoC][PATCH v3 "
` [GSoC][PATCH v3 1/4] rebase: duplicate git-rebase--interactive.sh to git-rebase--preserve-merges.sh
` [GSoC][PATCH v3 2/4] rebase: strip unused code in git-rebase--preserve-merges.sh
` [GSoC][PATCH v3 3/4] rebase: use the new git-rebase--preserve-merges.sh
` [GSoC][PATCH v3 4/4] rebase: remove -p code from git-rebase--interactive.sh
[PATCH] Clarify that a tag can refer to a non-commit object
2018-05-25 9:45 UTC
"man git-tag" inconsistent about whether you can tag non-commit objects
2018-05-25 9:40 UTC (5+ messages)
[PATCH v2] Use proper syntax for replaceables in command docs
2018-05-25 8:16 UTC (3+ messages)
BUG: No way to set fsck.<msg-id> when cloning
2018-05-25 7:36 UTC (20+ messages)
` [PATCH 0/4] fsck: doc fixes & fetch.fsck.* implementation
` [PATCH 1/4] config doc: don't describe *.fetchObjects twice
` [PATCH 2/4] config doc: unify the description of fsck.* and receive.fsck.*
` [PATCH 3/4] config doc: elaborate on what transfer.fsckObjects does
` [PATCH 4/4] fetch: implement fetch.fsck.*
unexpected "unresolved merge conflict" for a new file
2018-05-25 7:22 UTC (3+ messages)
git difftool with symlink to readonly jar failed
2018-05-25 6:23 UTC (3+ messages)
commit-graph: change in "best" merge-base when ambiguous
2018-05-25 6:03 UTC (5+ messages)
[PATCH 00/12] Integrate commit-graph into fsck, gc, and fetch
2018-05-25 4:11 UTC (30+ messages)
` [PATCH v2 00/12] Integrate commit-graph into fsck and gc
` [PATCH v2 03/12] commit-graph: test that 'verify' finds corruption
` [PATCH v3 00/20] Integrate commit-graph into 'fsck' and 'gc'
` [PATCH v3 01/20] commit-graph: UNLEAK before die()
` [PATCH v3 02/20] commit-graph: fix GRAPH_MIN_SIZE
` [PATCH v3 03/20] commit-graph: parse commit from chosen graph
` [PATCH v3 04/20] commit: force commit to parse from object database
` [PATCH v3 05/20] commit-graph: load a root tree from specific graph
` [PATCH v3 06/20] commit-graph: add 'verify' subcommand
` [PATCH v3 07/20] commit-graph: verify catches corrupt signature
` [PATCH v3 08/20] commit-graph: verify required chunks are present
` [PATCH v3 09/20] commit-graph: verify corrupt OID fanout and lookup
` [PATCH v3 10/20] commit-graph: verify objects exist
` [PATCH v3 11/20] commit-graph: verify root tree OIDs
` [PATCH v3 12/20] commit-graph: verify parent list
` [PATCH v3 13/20] commit-graph: verify generation number
` [PATCH v3 14/20] commit-graph: verify commit date
` [PATCH v3 15/20] commit-graph: test for corrupted octopus edge
` [PATCH v3 16/20] commit-graph: verify contents match checksum
` [PATCH v3 17/20] fsck: verify commit-graph
` [PATCH v3 18/20] commit-graph: add '--reachable' option
` [PATCH v3 19/20] gc: automatically write commit-graph files
` [PATCH v3 20/20] commit-graph: update design document
Wrong -dirty suffix set by setlocalversion (was: BUG in git diff-index)
2018-05-25 3:50 UTC (3+ messages)
[PATCH 0/5] Modernize some testcases for merge-recursive corner cases
2018-05-25 1:17 UTC (10+ messages)
` [PATCH 1/5] t6036, t6042: use test_create_repo to keep tests independent
` [PATCH 2/5] t6036, t6042: use test_line_count instead of wc -l
` [PATCH 3/5] t6036, t6042: prefer test_path_is_file, test_path_is_missing
` [PATCH 4/5] t6036, t6042: prefer test_cmp to sequences of test
` [PATCH 5/5] t6036: prefer test_when_finished to manual cleanup in following test
[RFC/PATCH 0/7] rerere: handle nested conflicts
2018-05-25 1:20 UTC (14+ messages)
` [RFC/PATCH 2/7] rerere: mark strings for translation
` [RFC/PATCH 3/7] rerere: add some documentation
` [RFC/PATCH 4/7] rerere: fix crash when conflict goes unresolved
` [RFC/PATCH 5/7] rerere: only return whether a path has conflicts or not
` [RFC/PATCH 7/7] rerere: teach rerere to handle nested conflicts
BUG: rev-parse segfault with invalid input
2018-05-25 1:07 UTC (14+ messages)
` [PATCH 1/2] t6101: add a test for rev-parse $garbage^@
` [PATCH 2/2] rev-parse: verify that commit looked up is not NULL
` [PATCH v2] rev-parse: check lookup'ed commit references for NULL
[PATCH] submodule: do not pass null OID to setup_revisions
2018-05-24 23:30 UTC (3+ messages)
why do "git log -h" and "git show -h" print the same thing?
2018-05-24 22:53 UTC (3+ messages)
Weird revision walk behaviour
2018-05-24 20:26 UTC (5+ messages)
[PATCH] Use proper syntax for replaceables in command docs
2018-05-24 20:07 UTC (3+ messages)
is the standard "[<options>]", and not "[options]" or other?
2018-05-24 19:15 UTC (2+ messages)
[PATCH v1 0/5] Allocate cache entries from memory pool
2018-05-24 14:47 UTC (13+ messages)
` [PATCH v3 0/7] allocate "
` [PATCH v3 1/7] read-cache: teach refresh_cache_entry() to take istate
` [PATCH v3 2/7] block alloc: add lifecycle APIs for cache_entry structs
` [PATCH v3 3/7] mem-pool: only search head block for available space
` [PATCH v3 4/7] mem-pool: add lifecycle management functions
` [PATCH v3 5/7] mem-pool: fill out functionality
` [PATCH v3 6/7] block alloc: allocate cache entries from mem_pool
` [PATCH v3 7/7] block alloc: add validations around cache_entry lifecyle
[RFC PATCH v3 1/2] Implement --first-parent for git rev-list --bisect
2018-05-24 4:31 UTC (2+ messages)
[RFC PATCH v3 2/2] Add tests for rev-list --bisect* --first-parent
2018-05-24 2:42 UTC (2+ messages)
[PATCH] Add initial support for pax extended attributes
2018-05-23 23:38 UTC (6+ messages)
` [PATCH v2 0/1] import-tars: read overlong names from pax extended header
` [PATCH v2 1/1] "
should config options be treated as case-sensitive?
2018-05-23 23:33 UTC (7+ messages)
[PATCHv6 0/1] git-p4: unshelve
2018-05-23 22:20 UTC (2+ messages)
` [PATCHv6 1/1] git-p4: add unshelve command
[PATCH 0/1] git-p4: unshelving: fix problem with newer P4
2018-05-23 19:38 UTC (10+ messages)
` [PATCH 1/1] git-p4: unshelve: use action==add instead of rev==none
` [PATCHv5 0/1] git-p4: unshelve: fix problem with newer p4d
` [PATCHv5 1/1] git-p4: add unshelve command
bug: --shallow-since misbehaves on old branch heads
2018-05-23 16:02 UTC (2+ messages)
git push => git: 'credential-winstore' is not a git command
2018-05-23 11:57 UTC (3+ messages)
which files are "known to git"?
2018-05-23 8:20 UTC (5+ messages)
[PATCH] config: free resources of `struct config_store_data`
2018-05-23 7:03 UTC (5+ messages)
` [PATCH v2 0/3] "
` [PATCH v2 3/3] config: let `config_store_data_clear()` handle `key`
[PATCH 1/2] remote-curl: accept all encoding supported by curl
2018-05-23 5:55 UTC (4+ messages)
` [PATCH v2 1/2] remote-curl: accept all encodings "
[PATCH] t: make many tests depend less on the refs being files
2018-05-23 5:33 UTC (6+ messages)
[RFC PATCH] fetch-pack: space out sent "haves" in negotiation
2018-05-23 3:42 UTC (2+ messages)
[GSoC] A blog about 'git stash' project
2018-05-23 3:20 UTC (9+ messages)
[PATCH] grep: handle corrupt index files early
2018-05-23 3:19 UTC (5+ messages)
` [PATCH 00/11]
` [PATCH 02/11] repository: introduce repo_read_index_or_die
` Why do we have both x*() and *_or_die() for "do or die"?
Officially supported Git versions
2018-05-23 3:16 UTC (2+ messages)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).