All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlisle T. Hamlin" <hamlin.carlisle@gmx.com>
To: Stephen Steves Linda Smith <ishchis2@gmail.com>, git@vger.kernel.org
Subject: Re: Can a note be pushed to origin?
Date: Tue, 1 Oct 2024 18:37:01 -0700	[thread overview]
Message-ID: <98470a2b-9a5c-4a22-a913-5098185afb65@gmx.com> (raw)
In-Reply-To: <20240925122918.1719619615FF@thunderbird.smith.home>

You betcha.

Add to the 'origin' entry in the config file specific to your local
repository:

fetch = +refs/notes/*:refs/notes/*
push = *refs/notes/*:refs/notes/*

Just be aware that other developers will remain blissfully unaware of
your notes unless they either expressly fetch notes for themselves, or
replicate your config setup as regards notes.

Good luck!

On 9/25/24 05:29, Stephen Steves Linda Smith wrote:
> In a project that I am working on, some metadata is currently embedded in some
> source files.  The question was asked yesterday if there is a way to move that
> metadata a git specific file and link it to the source file or commit.
>
> I remembered that git has notes which can be used to add such data to a
> commit, but I don't believe that such metadata gets pushed to origin nor
> fetched from origin but another user.
>
> Is there a currently implemented way to do something like this?
>


  reply	other threads:[~2024-10-02  1:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 12:29 Can a note be pushed to origin? Stephen Steves Linda Smith
2024-10-02  1:37 ` Carlisle T. Hamlin [this message]
2024-10-02  1:39   ` Carlisle T. Hamlin
  -- strict thread matches above, loose matches on Subject: below --
2024-09-25 12:25 Stephen P. Smith
2024-09-25 15:29 ` Kristoffer Haugsbakk
2024-09-27  4:15   ` Jeff King
2024-09-28  9:52     ` Kristoffer Haugsbakk
2024-09-25 12:07 Stephen P. Smith

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=98470a2b-9a5c-4a22-a913-5098185afb65@gmx.com \
    --to=hamlin.carlisle@gmx.com \
    --cc=git@vger.kernel.org \
    --cc=ishchis2@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.