git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <derrickstolee@github.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ds/branch-checked-out (was Re: What's cooking in git.git (Jun 2022, #03; Fri, 10))
Date: Mon, 13 Jun 2022 11:01:30 -0400	[thread overview]
Message-ID: <07eb5cce-2948-a653-a941-c8fe0924aee2@github.com> (raw)
In-Reply-To: <xmqqsfobc1hw.fsf@gitster.g>

On 6/10/2022 11:39 PM, Junio C Hamano wrote:

> * ds/branch-checked-out (2022-06-08) 4 commits
>  - branch: use branch_checked_out() when deleting refs
>  - fetch: use new branch_checked_out() and add tests
>  - branch: check for bisects and rebases
>  - branch: add branch_checked_out() helper
> 
>  Introduce a helper to see if a branch is already being worked on
>  (hence should not be newly checked out in a working tree), which
>  performs much better than the existing find_shared_symref() to
>  replace many uses of the latter.
> 
>  Will merge to 'next'?
>  source: <pull.1254.git.1654718942.gitgitgadget@gmail.com>

I sent a new patch that sits on top, fixing the memory leak
that you pointed out. Please take a look when you have time.

> --------------------------------------------------
> [Discarded]
> 
> * ds/rebase-update-refs (2022-06-07) 7 commits
>  . rebase: add rebase.updateRefs config option
>  . sequencer: implement 'update-refs' command
>  . rebase: add --update-refs option
>  . sequencer: add update-refs command
>  . sequencer: define array with enum values
>  . branch: add branch_checked_out() helper
>  . log-tree: create for_each_decoration()
> 
>  "git rebase" learns "--update-refs" to update the refs that point
>  at commits being rewritten so that they point at the corresponding
>  commits in the rewritten history.
> 
>  Retracted for possible future redesign.
>  cf. <pull.1254.git.1654718942.gitgitgadget@gmail.com>
>  source: <pull.1247.v2.git.1654634569.gitgitgadget@gmail.com>

Thanks. I will revisit this topic after the release window.

-Stolee

      parent reply	other threads:[~2022-06-13 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  3:39 What's cooking in git.git (Jun 2022, #03; Fri, 10) Junio C Hamano
2022-06-11 15:08 ` pb/range-diff-with-submodule (was: Re: What's cooking in git.git (Jun 2022, #03; Fri, 10)) Philippe Blain
2022-06-13 15:01 ` Derrick Stolee [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07eb5cce-2948-a653-a941-c8fe0924aee2@github.com \
    --to=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 NNTP newsgroup(s).