git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: johncai86 <johncai86@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2023, #01; Tue, 2)
Date: Wed, 3 May 2023 16:38:43 -0400	[thread overview]
Message-ID: <20230503203843.34xwgjdsnifnmzbf@pop-os> (raw)
In-Reply-To: <xmqqcz3ixsas.fsf@gitster.g>

On 23/05/02 03:49PM, Junio C Hamano wrote:
> Here are the topics that have been cooking in my tree.  Commits
> prefixed with '+' are in 'next' (being in 'next' is a sign that a
> topic is stable enough to be used and are candidate to be in a future
> release).  Commits prefixed with '-' are only in 'seen', and aren't
> considered "accepted" at all and may be annotated with an URL to a
> message that raises issues but they are no means exhaustive.  A
> topic without enough support may be discarded after a long period of
> no activity.

> --------------------------------------------------
> [New Topics]
> 
> * jc/attr-source-tree (2023-05-01) 1 commit
>  - attr: teach "--attr-source=<tree>" global option to "git"
> 
>  "git --attr-source=<tree> cmd $args" is a new way to have any
>  command to read attributes not from the working tree but from the
>  given tree object.
> 
>  Will merge to 'next'?
>  source: <pull.1470.v4.git.git.1682822352360.gitgitgadget@gmail.com>

Christian sent some more feedback on this one. Latest version: https://lore.kernel.org/git/pull.1470.v5.git.git.1683144574158.gitgitgadget@gmail.com/

thanks
John

  parent reply	other threads:[~2023-05-03 20:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 22:49 What's cooking in git.git (May 2023, #01; Tue, 2) Junio C Hamano
2023-05-03  3:48 ` Felipe Contreras
2023-05-03 17:36   ` Junio C Hamano
2023-05-03 20:38 ` johncai86 [this message]
2023-05-03 21:21   ` Junio C Hamano
2023-05-04 10:55 ` M Hickford
2023-05-04 15:13   ` Junio C Hamano

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=20230503203843.34xwgjdsnifnmzbf@pop-os \
    --to=johncai86@gmail.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).