From: Mahesh Vaidya <forvaidya@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-notes
Date: Thu, 24 Jun 2010 22:36:54 +0530 [thread overview]
Message-ID: <AANLkTimvCIQ-2lTtEvs94BuQvLerniIqdMaoUFKTZKLy@mail.gmail.com> (raw)
In-Reply-To: <AANLkTildVSt4cau9VhFePnmW057dQBEusCYKIk9NXgtb@mail.gmail.com>
Git Rocks !! ; I got it in man page
notes.rewriteMode Config Variable !!
When copying notes during a rewrite (see the
"notes.rewrite.<command>" option), determines what to do if the target
commit already has a note. Must be one of overwrite, concatenate, or
ignore. Defaults to concatenat
On Thu, Jun 24, 2010 at 10:23 PM, Mahesh Vaidya <forvaidya@gmail.com> wrote:
> How to Prevent git-notes removal / replacement by another user in master repo.?
>
> If I add "git notes" to my commit and Push it. How do my repo admin
> will ensure that notes are never overwritten or removed; but can be
> appended
>
> Thank You
>
--
Thank you and best regards.
Mahesh Vaidya / 9740500144
http://www.twitter.com/forvaidya
prev parent reply other threads:[~2010-06-24 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 16:53 git-notes Mahesh Vaidya
2010-06-24 17:06 ` Mahesh Vaidya [this message]
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=AANLkTimvCIQ-2lTtEvs94BuQvLerniIqdMaoUFKTZKLy@mail.gmail.com \
--to=forvaidya@gmail.com \
--cc=git@vger.kernel.org \
/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).