git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: Erik Cervin Edin <erik@cervined.in>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: git notes question
Date: Thu, 10 Mar 2022 14:26:55 +0100	[thread overview]
Message-ID: <1c967bd7f1536078b8972d5fc20bb1e4586f4bb1.camel@gmail.com> (raw)
In-Reply-To: <CA+JQ7M9HUMK8=b0+uxN9Kwx1VSH3OnxvdYTdw4ZoT9COHhJdeA@mail.gmail.com>

On Thu, 2022-03-10 at 14:11 +0100, Erik Cervin Edin wrote:
> > What I was asking was just if there was a way to not use these
> > default
> > strings.
> 
> Forgive me but I'm somewhat perplexed as to why you want to change
> it.
> Is there a specific use-case where this is a problem or is it a
> personal preference? Maybe you have a good reason and my imagination
> isn't stretching that far.
> 

I think there are some misunderstanding here :). I'm not requesting to
change it. I was just asking if there was a way (already implemented
and other than custom --format to get rid of it). And yes, this boils
down to personal preference and on how git-notes are typically written
in linux kernel mailing lists in patch series. I was actually writing
them by hand when I realized I could use git-notes and create patches
with them (and that these notes could "survive" to rebases so that it
would be easier to have them placed across versions of the series).

- Nuno Sá




  reply	other threads:[~2022-03-10 13:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 13:08 git notes question Nuno Sá
2022-03-09  8:54 ` Erik Cervin Edin
2022-03-09  9:11   ` Nuno Sá
2022-03-09 18:02     ` Junio C Hamano
2022-03-10  8:37       ` Nuno Sá
2022-03-10 13:11         ` Erik Cervin Edin
2022-03-10 13:26           ` Nuno Sá [this message]
2022-03-10 17:52         ` Junio C Hamano
2022-03-11  9:02           ` Nuno Sá

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=1c967bd7f1536078b8972d5fc20bb1e4586f4bb1.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=erik@cervined.in \
    --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).