All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git
Date: Fri, 02 Oct 2026 10:03:51 -0700	[thread overview]
Message-ID: <xmqqik3kxceg.fsf@gitster.g> (raw)
In-Reply-To: <20261002165407.36721-1-jayatheerthkulkarni2005@gmail.com> (K. Jayatheerth's message of "Fri, 2 Oct 2026 22:24:06 +0530")

K Jayatheerth <jayatheerthkulkarni2005@gmail.com> writes:

>>* kj/repo-info-more-path-keys (2026-09-11) 7 commits
>> - repo: add path.cdup
>> - repo: add path.git-prefix
>> - repo: add path.grafts with absolute and relative suffixes
>> - repo: add path.index with absolute and relative suffixes
>> - repo: add path.hooks with absolute and relative suffixes
>> - repo: add path.superproject-root with absolute and relative suffixes
>> - repo: add path.toplevel with absolute and relative suffix formatting
>>
>> The 'git repo info' command has been taught more keys to output
>> paths of various repository components (such as the working tree
>> root, superproject working tree, object database, etc.), supporting
>> both absolute and relative path formats.
>>
>> Expecting a reroll.
>> cf. <CA+rGoLcRRZPu8SD-vZw+rEjVzKO02=nMn_x+4ANJX7eh9jgBcw@mail.gmail.com>
>> source: <20260911144519.1011780-1-jayatheerthkulkarni2005@gmail.com>
>
> Hey Junio, I have sent a new series at the message ID
> <20260927114420.59724-1-jayatheerthkulkarni2005@gmail.com>

Will replace.  Thanks.

  reply	other threads:[~2026-10-02 17:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 22:48 What's cooking in git.git (Oct 2026, #01) Junio C Hamano
2026-10-02  9:10 ` Patrick Steinhardt
2026-10-02 15:02   ` Junio C Hamano
2026-10-02 16:54 ` What's cooking in git.git K Jayatheerth
2026-10-02 17:03   ` Junio C Hamano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-05 22:55 Junio C Hamano
2015-08-05 23:14 ` David Turner
2015-08-05 23:58   ` Junio C Hamano
2015-08-07 16:40     ` Junio C Hamano
2015-08-06  4:55 ` Jeff King
2015-08-07 18:47   ` Junio C Hamano
2015-08-06 10:19 ` Johannes Schindelin
2006-12-13 21:38 Junio C Hamano
2006-01-12  0:04 Junio C Hamano
2006-01-14  3:45 ` Junio C Hamano
2006-01-16 10:53 ` Petr Baudis

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=xmqqik3kxceg.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jayatheerthkulkarni2005@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.