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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
A preview release 2.24-rc0 has bee
On Tue, Oct 15, 2019 at 6:25 PM Junio C Hamano wrote:
>
> Elijah Newren writes:
>
> >> * en/merge-recursive-directory-rename-fixes (2019-10-12) 2 commits
> >> (merged to 'next' on 2019-10-15 at ebfdc3ff7b)
> >> + merge-recursive: fix merging a subdirectory into the root directory
> >> + merge
Elijah Newren writes:
>> * en/merge-recursive-directory-rename-fixes (2019-10-12) 2 commits
>> (merged to 'next' on 2019-10-15 at ebfdc3ff7b)
>> + merge-recursive: fix merging a subdirectory into the root directory
>> + merge-recursive: clean up get_renamed_dir_portion()
>>
>> A few glitches
Derrick Stolee writes:
> On 10/15/2019 3:11 AM, Eric Wong wrote:
>> Junio C Hamano wrote:
>>> Eric Wong writes:
>>>
I just took a brief look, but that appears to leak memory.
"hashmap_free(var, 1)" should be replaced with
"hashmap_free_entries(var, struct foo, member)"
On Tue, Oct 15, 2019 at 10:39 AM Johannes Schindelin
wrote:
>
> Hi Elijah,
>
> On Tue, 15 Oct 2019, Elijah Newren wrote:
>
> > On Tue, Oct 15, 2019 at 2:04 AM Junio C Hamano wrote:
> > > * en/fast-imexport-nested-tags (2019-10-04) 8 commits
> > > (merged to 'next' on 2019-10-07 at 3e75779e10)
>
Hi Elijah,
On Tue, 15 Oct 2019, Elijah Newren wrote:
> On Tue, Oct 15, 2019 at 2:04 AM Junio C Hamano wrote:
> > * en/fast-imexport-nested-tags (2019-10-04) 8 commits
> > (merged to 'next' on 2019-10-07 at 3e75779e10)
> > + fast-export: handle nested tags
> > + t9350: add tests for tags of t
On Tue, Oct 15, 2019 at 2:04 AM Junio C Hamano wrote:
> * en/fast-imexport-nested-tags (2019-10-04) 8 commits
> (merged to 'next' on 2019-10-07 at 3e75779e10)
> + fast-export: handle nested tags
> + t9350: add tests for tags of things other than a commit
> + fast-export: allow user to request
On 10/15/2019 3:11 AM, Eric Wong wrote:
> Junio C Hamano wrote:
>> Eric Wong writes:
>>
>>> I just took a brief look, but that appears to leak memory.
>>>
>>> "hashmap_free(var, 1)" should be replaced with
>>> "hashmap_free_entries(var, struct foo, member)"
>>>
>>> Only "hashmap_free(var, 0)" can
Junio C Hamano wrote:
> Eric Wong writes:
>
> > I just took a brief look, but that appears to leak memory.
> >
> > "hashmap_free(var, 1)" should be replaced with
> > "hashmap_free_entries(var, struct foo, member)"
> >
> > Only "hashmap_free(var, 0)" can become "hashmap_free(var)"
>
> I delibera
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
You can find the changes described
Eric Wong writes:
> I just took a brief look, but that appears to leak memory.
>
> "hashmap_free(var, 1)" should be replaced with
> "hashmap_free_entries(var, struct foo, member)"
>
> Only "hashmap_free(var, 0)" can become "hashmap_free(var)"
I deliberately avoided merge-time band-aid fixups on
Johannes Schindelin wrote:
> On Fri, 11 Oct 2019, Junio C Hamano wrote:
> > * ds/sparse-cone (2019-10-08) 17 commits
> > - sparse-checkout: cone mode should not interact with .gitignore
> > - sparse-checkout: write using lockfile
> > - sparse-checkout: update working directory in-process
> > -
Hi Junio,
On Fri, 11 Oct 2019, Junio C Hamano wrote:
> * ds/sparse-cone (2019-10-08) 17 commits
> - sparse-checkout: cone mode should not interact with .gitignore
> - sparse-checkout: write using lockfile
> - sparse-checkout: update working directory in-process
> - sparse-checkout: sanitize f
Junio C Hamano writes:
> By the way, I think I made a mistake in my calendar math.
>
> This topic was merged to 'next' on the 7th and it is not especially
> tricky; unless I (or somebody else) find glaring issues in it during
> the final sanity check before merging it to 'master' during the next
Elijah Newren writes:
> Did I shoot myself in the foot by being quick to jump on Rene's couple
> of cosmetic touch-up suggestions he posted over a week after the
> series was originally posted?
If the suggested updates were simple enough to do and would improve
the result sufficiently (which is
On Fri, Oct 11, 2019 at 9:42 AM Junio C Hamano wrote:
>
> Elijah Newren writes:
>
> >> * en/fast-imexport-nested-tags (2019-10-04) 8 commits
> >> (merged to 'next' on 2019-10-07 at 3e75779e10)
> >> + fast-export: handle nested tags
> >> ...
> >> + fast-export: fix exporting a tag and nothing
Elijah Newren writes:
>> * en/fast-imexport-nested-tags (2019-10-04) 8 commits
>> (merged to 'next' on 2019-10-07 at 3e75779e10)
>> + fast-export: handle nested tags
>> ...
>> + fast-export: fix exporting a tag and nothing else
>>
>> Updates to fast-import/export.
>>
>> Will merge to 'mast
On Fri, Oct 11, 2019 at 12:35 AM Junio C Hamano wrote:
> [Cooking]
[...]
> * en/fast-imexport-nested-tags (2019-10-04) 8 commits
> (merged to 'next' on 2019-10-07 at 3e75779e10)
> + fast-export: handle nested tags
> + t9350: add tests for tags of things other than a commit
> + fast-export:
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
We may want to merge down fixes ac
On Tue, Oct 08, 2019 at 09:36:26PM +0200, Johannes Schindelin wrote:
> I missed a well-ACKed contribution in here: the code of conduct Peff
> kindly submitted, with the add-on that clarifies who is in that group of
> potential mediators. See
>
> https://public-inbox.org/git/20190924064454.ga30...@
Hi Junio,
On Mon, 7 Oct 2019, Junio C Hamano wrote:
> 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 ones marked with '.' do not appear in any of
> the integration branches, but I a
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
You can find the changes described
Phillip Wood writes:
>> * ra/rebase-i-more-options (2019-09-09) 6 commits
>> ...
>> Is this ready for 'next'.
>
> Nearly, but not quite I think cf [1]. Also I'm still not convinced
> that having different behaviors for --ignore-whitespace depending on
> the backend is going to be helpful but ma
Hi Elijah
On 05/10/2019 01:40, Elijah Newren wrote:
On Fri, Oct 4, 2019 at 4:49 AM Phillip Wood wrote:
Hi Junio
On 03/10/2019 06:04, Junio C Hamano wrote:
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'
On Fri, Oct 4, 2019 at 4:49 AM Phillip Wood wrote:
>
> Hi Junio
>
> On 03/10/2019 06:04, Junio C Hamano wrote:
> > 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 ones marked with
Hi Junio
On 03/10/2019 06:04, Junio C Hamano wrote:
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 ones marked with '.' do not appear in any of
the integration branches, but I am still
Elijah Newren writes:
> Actually, René posted a code cleanup suggestion for patch 2/8, so I
> sent a V3 re-roll[1]. Could you pick up V3 instead of merging V2 down
> to next?
>
> [1] https://public-inbox.org/git/20191003202709.26279-1-new...@gmail.com/
Thanks for stopping me.
Will take a look.
Emily Shaffer writes:
> On Thu, Oct 03, 2019 at 02:04:39PM +0900, Junio C Hamano wrote:
>> 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 ones marked with '.' do not appear in any
On Wed, Oct 2, 2019 at 10:22 PM Junio C Hamano wrote:
>
> * en/fast-imexport-nested-tags (2019-10-02) 8 commits
> - fast-export: handle nested tags
> - t9350: add tests for tags of things other than a commit
> - fast-export: allow user to request tags be marked with --mark-tags
> - fast-export
On Thu, Oct 03, 2019 at 02:04:39PM +0900, Junio C Hamano wrote:
> 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 ones marked with '.' do not appear in any of
> the integration branche
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
You can find the changes described
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
I've been offline for a week or so
On 2019-09-28 at 23:31:33, Junio C Hamano wrote:
> "brian m. carlson" writes:
>
> > On 2019-09-07 at 17:26:53, Junio C Hamano wrote:
> >> * bc/object-id-part17 (2019-08-19) 26 commits
> >> ...
> >> - builtin/replace: make hash size independent
> >>
> >> Preparation for SHA-256 upgrade continue
"brian m. carlson" writes:
> On 2019-09-07 at 17:26:53, Junio C Hamano wrote:
>> * bc/object-id-part17 (2019-08-19) 26 commits
>> ...
>> - builtin/replace: make hash size independent
>>
>> Preparation for SHA-256 upgrade continues.
>>
>> Looked mostly OK, with a possible update.
>> cf. <201
On 26/09/19 08:44PM, Johannes Schindelin wrote:
> Hi,
>
> On Tue, 24 Sep 2019, Pratyush Yadav wrote:
>
> > On 23/09/19 09:35PM, Johannes Schindelin wrote:
> > > Hi,
> > >
> > > On Wed, 18 Sep 2019, Junio C Hamano wrote:
> > >
> > > > We have a new maintainer for git-gui now. Thanks Pratyush for
Hi,
On Tue, 24 Sep 2019, Pratyush Yadav wrote:
> On 23/09/19 09:35PM, Johannes Schindelin wrote:
> > Hi,
> >
> > On Wed, 18 Sep 2019, Junio C Hamano wrote:
> >
> > > We have a new maintainer for git-gui now. Thanks Pratyush for
> > > volunteering.
> >
> > Excellent!
> >
> > I opened PRs at https
On 23/09/19 09:35PM, Johannes Schindelin wrote:
> Hi,
>
> On Wed, 18 Sep 2019, Junio C Hamano wrote:
>
> > We have a new maintainer for git-gui now. Thanks Pratyush for
> > volunteering.
>
> Excellent!
>
> I opened PRs at https://github.com/prati0100/git-gui/pulls. Pratyush, do
> you accept co
Hi,
On Wed, 18 Sep 2019, Junio C Hamano wrote:
> We have a new maintainer for git-gui now. Thanks Pratyush for
> volunteering.
Excellent!
I opened PRs at https://github.com/prati0100/git-gui/pulls. Pratyush, do
you accept contributions in this form, or should I do anything
differently?
Ciao,
Taylor Blau writes:
> commit-graph files on all repositories hosted on GitHub, and some
> corrupt repositories triggered the behavior.
> ...
> We've been running this patch since a few days before I submitted it to
> ...
> This one has a similar origin story, and has also been running at GitHub
>
On Wed, Sep 18, 2019 at 03:33:15PM -0700, Junio C Hamano wrote:
> * tb/commit-graph-harden (2019-09-09) 3 commits
> - commit-graph.c: handle corrupt/missing trees
> - commit-graph.c: handle commit parsing errors
> - t/t5318: introduce failing 'git commit-graph write' tests
>
> The code to parse
Thomas Gummerer writes:
> I have sent an updated version of this, that integrates the changes
> the js/builtin-add-i topic needs in [*1*]. I think it would be ok to
> pick up that version and keep js/builtin-add-i out of pu until it's
> rebased on top of that.
Thanks, will replace after looking
Martin Ågren writes:
> Hi Junio,
>
> On Thu, 19 Sep 2019 at 01:44, Junio C Hamano wrote:
>
>> * ma/asciidoctor-refmiscinfo (2019-09-16) 3 commits
>> - doc-diff: replace --cut-header-footer with --cut-footer
>> - asciidoctor-extensions: provide ``
>> - Doc/Makefile: give mansource/-version/-ma
Jonathan Tan writes:
>> * jt/cache-tree-avoid-lazy-fetch-during-merge (2019-09-09) 1 commit
>> - cache-tree: do not lazy-fetch tentative tree
>>
>> The cache-tree code has been taught to be less aggressive in
>> attempting to see if a tree object it computed already exists in
>> the reposito
On 09/18, Junio C Hamano wrote:
> * tg/stash-refresh-index (2019-09-05) 3 commits
> - stash: make sure to write refreshed cache
> - merge: use refresh_and_write_cache
> - factor out refresh_and_write_cache function
>
> "git stash" learned to write refreshed index back to disk.
>
> Needs coor
Hi Junio,
On Thu, 19 Sep 2019 at 01:44, Junio C Hamano wrote:
> * ma/asciidoctor-refmiscinfo (2019-09-16) 3 commits
> - doc-diff: replace --cut-header-footer with --cut-footer
> - asciidoctor-extensions: provide ``
> - Doc/Makefile: give mansource/-version/-manual attributes
>
> Update suppo
> * jt/cache-tree-avoid-lazy-fetch-during-merge (2019-09-09) 1 commit
> - cache-tree: do not lazy-fetch tentative tree
>
> The cache-tree code has been taught to be less aggressive in
> attempting to see if a tree object it computed already exists in
> the repository.
>
> Waiting for a respo
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
We have a new maintainer for git-g
On Mon, 16 Sep 2019 10:43:28 PDT (-0700), gits...@pobox.com wrote:
Palmer Dabbelt writes:
... It looks
like there are some test failures when I rebase to the latest master,
which I'm happy to fix. Just let me know if I should:
* Send just the first 4 patches, holding onto the last one for
Palmer Dabbelt writes:
> ... It looks
> like there are some test failures when I rebase to the latest master,
> which I'm happy to fix. Just let me know if I should:
> * Send just the first 4 patches, holding onto the last one for later.
> ...
> * Send just a single patch, which wouldn't add t
On Thu, 12 Sep 2019 11:02:42 PDT (-0700), gits...@pobox.com wrote:
Johannes Schindelin writes:
* pd/fetch-jobs (2019-08-13) 5 commits
. fetch: make --jobs control submodules and remotes
. fetch: add the --submodule-fetch-jobs option
. fetch: add the fetch.jobs config key
. fetch: add the "
Johannes Schindelin writes:
>> * pd/fetch-jobs (2019-08-13) 5 commits
>> . fetch: make --jobs control submodules and remotes
>> . fetch: add the --submodule-fetch-jobs option
>> . fetch: add the fetch.jobs config key
>> . fetch: add the "--fetch-jobs" option
>> . fetch: rename max_children t
Hi Junio,
On Sat, 7 Sep 2019, Junio C Hamano wrote:
> * pd/fetch-jobs (2019-08-13) 5 commits
> . fetch: make --jobs control submodules and remotes
> . fetch: add the --submodule-fetch-jobs option
> . fetch: add the fetch.jobs config key
> . fetch: add the "--fetch-jobs" option
> . fetch: ren
Hi, Junio
On Sat, Sep 7, 2019 at 2:27 PM Junio C Hamano wrote:
>
> * mt/threaded-grep-in-object-store (2019-08-13) 4 commits
> - grep: re-enable threads in some non-worktree cases
> - grep: disable grep_read_mutex when possible
> - grep: allow locks to be enabled individually
> - object-store
On 2019.09.07 10:26, Junio C Hamano wrote:
> * js/trace2-json-schema (2019-07-25) 3 commits
> . ci: run trace2 schema validation in the CI suite
> . trace2: add a schema validator for trace2 events
> . trace2: add a JSON schema for trace2 events
>
> The JSON output produced by "trace2" subsyst
Hi Junio,
On Sun, 8 Sep 2019 at 14:51, Junio C Hamano wrote:
>
> * ma/asciidoctor-refmiscinfo (2019-09-03) 2 commits
> - doc-diff: replace --cut-header-footer with --cut-footer
> - asciidoctor-extensions: provide ``
>
> Update support for Asciidoctor documentation toolchain.
>
> Will merge to
"brian m. carlson" writes:
> On 2019-09-07 at 17:26:53, Junio C Hamano wrote:
>> * bc/object-id-part17 (2019-08-19) 26 commits
>> - midx: switch to using the_hash_algo
>> ...
>> - builtin/replace: make hash size independent
>>
>> Preparation for SHA-256 upgrade continues.
>>
>> Looked most
On Mon, Sep 09, 2019 at 12:57:17PM -0700, Junio C Hamano wrote:
> Denton Liu writes:
>
> > Hi Junio,
> >
> > On Sat, Sep 07, 2019 at 10:26:53AM -0700, Junio C Hamano wrote:
> >> * dl/complete-cherry-pick-revert-skip (2019-08-27) 3 commits
> >> - status: mention --skip for revert and cherry-pick
On 2019-09-07 at 17:26:53, Junio C Hamano wrote:
> * bc/object-id-part17 (2019-08-19) 26 commits
> - midx: switch to using the_hash_algo
> - builtin/show-index: replace sha1_to_hex
> - rerere: replace sha1_to_hex
> - builtin/receive-pack: replace sha1_to_hex
> - builtin/index-pack: replace sha
Denton Liu writes:
> Hi Junio,
>
> On Sat, Sep 07, 2019 at 10:26:53AM -0700, Junio C Hamano wrote:
>> * dl/complete-cherry-pick-revert-skip (2019-08-27) 3 commits
>> - status: mention --skip for revert and cherry-pick
>> - completion: add --skip for cherry-pick and revert
>> - completion: merg
Hi Junio,
On Sat, Sep 07, 2019 at 10:26:53AM -0700, Junio C Hamano wrote:
> * dl/complete-cherry-pick-revert-skip (2019-08-27) 3 commits
> - status: mention --skip for revert and cherry-pick
> - completion: add --skip for cherry-pick and revert
> - completion: merge options for cherry-pick and
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
The tip of 'next' has been rewound
Carlo Arenas writes:
> On Fri, Aug 23, 2019 at 6:16 PM Junio C Hamano wrote:
>>
>> * cb/pcre2-chartables-leakfix (2019-08-06) 3 commits
>> - grep: avoid leak of chartables in PCRE2
>> - grep: make PCRE2 aware of custom allocator
>> - grep: make PCRE1 aware of custom allocator
>>
>> WIP
>
> t
On Fri, Aug 23, 2019 at 6:16 PM Junio C Hamano wrote:
>
> * cb/pcre2-chartables-leakfix (2019-08-06) 3 commits
> - grep: avoid leak of chartables in PCRE2
> - grep: make PCRE2 aware of custom allocator
> - grep: make PCRE1 aware of custom allocator
>
> WIP
this was v3 and doesn't sufficiently
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
The tip of 'next' has been rewound
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
The first batch of topics post 2.2
Matheus Tavares Bernardino writes:
>> Thanks. Or we could just go the lazier route. A new stable release
>> would happen within a day or two, and then in a week or so after that,
>> the tip of 'next' gets rewound and rebuilt on top of it. We can
>> discard the older copy and replace with the n
On Thu, Aug 15, 2019 at 1:57 PM Junio C Hamano wrote:
>
> Carlo Arenas writes:
>
> > On Wed, Aug 14, 2019 at 4:58 PM Matheus Tavares Bernardino
> > wrote:
> >>
> >> On Wed, Aug 14, 2019 at 6:27 PM Junio C Hamano wrote:
> >> >
> >> [...]
> >> > * mt/grep-submodules-working-tree (2019-07-30) 1 co
Carlo Arenas writes:
> On Wed, Aug 14, 2019 at 4:58 PM Matheus Tavares Bernardino
> wrote:
>>
>> On Wed, Aug 14, 2019 at 6:27 PM Junio C Hamano wrote:
>> >
>> [...]
>> > * mt/grep-submodules-working-tree (2019-07-30) 1 commit
>> > (merged to 'next' on 2019-08-02 at e1a46a195f)
>> > + grep: f
On Wed, Aug 14, 2019 at 4:58 PM Matheus Tavares Bernardino
wrote:
>
> On Wed, Aug 14, 2019 at 6:27 PM Junio C Hamano wrote:
> >
> [...]
> > * mt/grep-submodules-working-tree (2019-07-30) 1 commit
> > (merged to 'next' on 2019-08-02 at e1a46a195f)
> > + grep: fix worktree case in submodules
>
>
Hi, Junio
On Wed, Aug 14, 2019 at 6:27 PM Junio C Hamano wrote:
>
[...]
> * mt/grep-submodules-working-tree (2019-07-30) 1 commit
> (merged to 'next' on 2019-08-02 at e1a46a195f)
> + grep: fix worktree case in submodules
There is a new version of this patch here[1], addressing the comments
yo
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
We have a handful of topics in 'ne
On August 11, 2019 8:39 PM, Junio C Hamano wrote:
> Jeff King writes:
>
> > IMHO scripting around "action" commands like checkout is less bad than
> > around "output" commands like log. The general action of "switch to
> > this branch" is unlikely to be changed much over the years (or via
> > con
Jeff King writes:
> IMHO scripting around "action" commands like checkout is less bad than
> around "output" commands like log. The general action of "switch to this
> branch" is unlikely to be changed much over the years (or via config),
> but the output of log, etc, is.
>
> There are no guarant
On Fri, Aug 09, 2019 at 11:05:34AM -0700, Phil Hord wrote:
> On Fri, Aug 9, 2019 at 10:48 AM Junio C Hamano wrote:
> >
> > Jeff King writes:
> >
> > > I don't know of any plans for checkout in particular, but I think the
> > > docs for restore/switch make it clear that it's way too early to star
On August 9, 2019 1:45 PM, Junio C Hamano wrote:
> "Randall S. Becker" writes:
>
> > On 01 Aug 2019 13:05:12, Junio wrote:
> >> >> *snip*
> >
> > I think this got missed in the shuffle, but I am getting questions
> > about the topic from my own team that I cannot answer.
> >
> > I noticed that th
On Fri, Aug 9, 2019 at 10:48 AM Junio C Hamano wrote:
>
> Jeff King writes:
>
> > I don't know of any plans for checkout in particular, but I think the
> > docs for restore/switch make it clear that it's way too early to start
> > scripting around them:
> >
> > $ git grep EXPERIMENTAL Documenta
Jeff King writes:
> I don't know of any plans for checkout in particular, but I think the
> docs for restore/switch make it clear that it's way too early to start
> scripting around them:
>
> $ git grep EXPERIMENTAL Documentation/
> Documentation/git-restore.txt:THIS COMMAND IS EXPERIMENTAL.
"Randall S. Becker" writes:
> On 01 Aug 2019 13:05:12, Junio wrote:
>> >> *snip*
>
> I think this got missed in the shuffle, but I am getting questions
> about the topic from my own team that I cannot answer.
>
> I noticed that the switch and restore commands are now available
> in 2.23.0 but are
On Fri, Aug 9, 2019 at 4:41 AM Jeff King wrote:
>
> On Thu, Aug 08, 2019 at 08:07:36PM -0700, Phil Hord wrote:
>
> > The long form you give there is to be used in case the old email
> > address is not a unique key. See 'git help shortlog'.
> >
> > The problem we have at work is that one woman's ol
On August 9, 2019 12:29 PM, Jeff King wrote:
> On Fri, Aug 09, 2019 at 10:06:06AM -0400, Randall S. Becker wrote:
>
> > On 01 Aug 2019 13:05:12, Junio wrote:
> > > >> *snip*
> >
> > I think this got missed in the shuffle, but I am getting questions about the
> topic from my own team that I cannot
On Fri, Aug 09, 2019 at 10:06:06AM -0400, Randall S. Becker wrote:
> On 01 Aug 2019 13:05:12, Junio wrote:
> > >> *snip*
>
> I think this got missed in the shuffle, but I am getting questions about the
> topic from my own team that I cannot answer.
>
> I noticed that the switch and restore comm
On 01 Aug 2019 13:05:12, Junio wrote:
> >> *snip*
I think this got missed in the shuffle, but I am getting questions about the
topic from my own team that I cannot answer.
I noticed that the switch and restore commands are now available in 2.23.0 but
are not discussed in recent What's Cooking o
On Thu, Aug 08, 2019 at 08:07:36PM -0700, Phil Hord wrote:
> The long form you give there is to be used in case the old email
> address is not a unique key. See 'git help shortlog'.
>
> The problem we have at work is that one woman's old email address
> includes her deadname, like . I will
> lea
Hi Ariadne,
On Thu, Aug 08, 2019 at 10:21:02PM -0500, Ariadne Conill wrote:
> Hello,
>
> On Thu, Aug 8, 2019 at 10:07 PM Phil Hord wrote:
> >
> > The issue of deadnaming aside, turning on log.mailmap by default is
> > the sensible thing to do given that other Git features already honor
> > it tha
Hello,
On Thu, Aug 8, 2019 at 10:07 PM Phil Hord wrote:
>
> The issue of deadnaming aside, turning on log.mailmap by default is
> the sensible thing to do given that other Git features already honor
> it that way. Having it ignored-by-default (but only sometimes) just
> adds confusion when a mai
The issue of deadnaming aside, turning on log.mailmap by default is
the sensible thing to do given that other Git features already honor
it that way. Having it ignored-by-default (but only sometimes) just
adds confusion when a mailmap is available.
> > > - The '.mailmap' provides a list of trans
Hello,
On Thu, Aug 8, 2019 at 9:07 PM Taylor Blau wrote:
>
> Hi Ariadne,
>
> Thank you for replying. I'm replying myself to the quoted hunks below,
> and I very much appreciate your input. I would like to note that I
> myself did not come up with these concerns alone, they were merely
> suggested
Hi Ariadne,
Thank you for replying. I'm replying myself to the quoted hunks below,
and I very much appreciate your input. I would like to note that I
myself did not come up with these concerns alone, they were merely
suggested to me by a coworker, and I found them concerning.
I am not myself tran
Hello,
On August 8, 2019 8:13:15 PM EDT, Taylor Blau wrote:
>Hi Junio,
>
>On Thu, Jul 25, 2019 at 05:19:23PM -0700, Junio C Hamano wrote:
>> Here are the topics that have been cooking. Commits prefixed with
>> '-' are only in 'pu' (proposed updates) while commits prefixed with
>> '+' are in 'nex
Hi Junio,
On Thu, Jul 25, 2019 at 05:19:23PM -0700, Junio C Hamano wrote:
> 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 ones marked with '.' do not appear in any of
> the integrat
Matthew DeVore writes:
> On Tue, Aug 06, 2019 at 02:58:38PM -0700, Junio C Hamano wrote:
>>
>> * md/list-objects-filter-combo (2019-06-28) 10 commits
>> - list-objects-filter-options: make parser void
>> - list-objects-filter-options: clean up use of ALLOC_GROW
>> - list-objects-filter-option
On Tue, Aug 06, 2019 at 02:58:38PM -0700, Junio C Hamano wrote:
>
> * md/list-objects-filter-combo (2019-06-28) 10 commits
> - list-objects-filter-options: make parser void
> - list-objects-filter-options: clean up use of ALLOC_GROW
> - list-objects-filter-options: allow mult. --filter
> - str
Rohit Ashiwal writes:
> On Tue, 06 Aug 2019 14:58:38 -0700 Junio C Hamano wrote:
>>
>> [...]
>> * ra/rebase-i-more-options (2019-07-23) 4 commits
>> ...
>> Needs a bit of fixups, at least.
>> [...]
>
> This patch series was re-sent as a new topic, available here[1].
Thanks for a pointer.
Dur
Hi Junio
On Tue, 06 Aug 2019 14:58:38 -0700 Junio C Hamano wrote:
>
> [...]
> * ra/rebase-i-more-options (2019-07-23) 4 commits
> - SQUASH???
> - rebase -i: support --committer-date-is-author-date
> - sequencer: add NULL checks under read_author_script
> - rebase -i: add --ignore-whitespace f
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
There are a few last-minute fix-up
Johannes Schindelin writes:
>> Yup. I think they are now in good shape to be among the first to
>> graduate post release. Building the warning facility necessary to
>> start dropping the $GIT_DIR/branches/ support would be too late for
>> this cycle, but now this topic is independent from that,
Hi Junio,
On Fri, 2 Aug 2019, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> >
> > On Thu, 1 Aug 2019, Junio C Hamano wrote:
> >
> >> * js/visual-studio (2019-07-29) 23 commits
> >> - git: avoid calling aliased builtins via their dashed form
> >> - bin-wrappers: append `.exe` to targe
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 ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
The first release candidate for 2.
On Fri, Aug 02, 2019 at 02:12:34PM +0200, Johannes Schindelin wrote:
> > > * js/early-config-with-onbranch (2019-07-31) 1 commit
> > > (merged to 'next' on 2019-08-01 at 26b713c824)
> > > + config: work around bug with includeif:onbranch and early config
> > >
> > > The recently added [include
Johannes Schindelin writes:
> Hi Junio,
>
> On Thu, 1 Aug 2019, Junio C Hamano wrote:
>
>> * js/visual-studio (2019-07-29) 23 commits
>> - git: avoid calling aliased builtins via their dashed form
>> - bin-wrappers: append `.exe` to target paths if necessary
>> - .gitignore: ignore Visual Stud
1 - 100 of 3241 matches
Mail list logo
