git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Apr 2019, #01; Thu, 4)

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Apr 6, 2019, 19:57 UTC
Message-ID
<87ef6eaoub.fsf@evledraar.gmail.com>
In-Reply-To
<xmqqr2aidpxw.fsf@gitster-ct.c.googlers.com>
On Thu, Apr 04 2019, Junio C Hamano wrote:
Show 12 quoted lines
> * dl/rebase-i-keep-base (2019-04-03) 4 commits
>  - rebase: teach rebase --keep-base
>  - rebase: fast-forward --onto in more cases
>  - t3432: test rebase fast-forward behavior
>  - t3431: add rebase --fork-point tests
>
>  "git rebase --keep-base <upstream>" tries to find the original base
>  of the topic being rebased and rebase on top of that same base, which
>  is useful when running the "git rebase -i" (and its limited variant
>  "git rebase -x").
>
>  Will merge to 'next'.

Still a bit unclear on whether parts of this are intended or just emergent behavior, as noted in https://public-inbox.org/git/87ftquapfy.fsf@evledraar.gmail.com/

Show 15 quoted lines
> * jh/trace2-sid-fix (2019-04-01) 7 commits
>  - trace2: make SIDs more unique
>  - trace2: clarify UTC datetime formatting
>  - trace2: report peak memory usage of the process
>  - trace2: use system config for default trace2 settings
>  - trace2: find exec-dir before trace2 initialization
>  - trace2: add absolute elapsed time to start event
>  - trace2: refactor setting process starting time
>
>  Polishing of the new trace2 facility continues.  The system-level
>  configuration can specify site-wide trace2 settings (which would be
>  loved by big-brother types ;-).
>
>  Getting closer but still being discussed.
>  cf. <20190403000032.GA190454@google.com>
FWIW also the discussion as of https://public-inbox.org/git/87lg0x9voz.fsf@evledraar.gmail.com/
Show 7 quoted lines
> * js/trace2-to-directory (2019-03-22) 1 commit
>  - trace2: write to directory targets
>
>  The trace2 tracing facility learned to auto-generate a filename
>  when told to log to a directory.
>
>  Will merge to 'next'.

I had the feedback of effectively "why retry if we can just make the SID unique enough" in https://public-inbox.org/git/874l7rcqk9.fsf@evledraar.gmail.com/ on March 25th.

You seemed to think so, but after Jeff Hostetler made the SID more unique (AFAICT "actually unique" in practice) in the parallel in-flight jh/trace2-sid-fix (https://public-inbox.org/git/4352952677a11776a18ec9b6862cf358307cfafd.1553879063.git.gitgitgadget@gmail.com/)

I think it's fine to merge js/trace2-to-directory down as it is, but do you/Josh think that retry logic needs to stay with that sort of SID?

Previous: Junio C HamanoNext: Junio C Hamano
Message 17 of 19 in “What's cooking in git.git (Apr 2019, #01; Thu, 4)”
  1. Junio C HamanoApr 4, 2019
  2. Duy NguyenApr 4, 2019
  3. Junio C HamanoApr 4, 2019
  4. Ævar Arnfjörð BjarmasonApr 6, 2019
  5. Junio C HamanoApr 8, 2019
  6. Introduce "precious" file conceptNguyễn Thái Ngọc Duy, Apr 9, 2019
  7. Junio C HamanoApr 9, 2019
  8. Duy NguyenApr 10, 2019
  9. Junio C HamanoApr 12, 2019
  10. Eric SunshineApr 9, 2019
  11. Ævar Arnfjörð BjarmasonApr 12, 2019
  12. Duy NguyenApr 13, 2019
  13. Todd ZullingerApr 5, 2019
  14. Junio C HamanoApr 5, 2019
  15. Ævar Arnfjörð BjarmasonApr 6, 2019
  16. Junio C HamanoApr 8, 2019
  17. Ævar Arnfjörð BjarmasonApr 6, 2019
  18. Junio C HamanoApr 8, 2019
  19. Josh SteadmonApr 8, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.