git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jelmer Vernooij <jelmer@samba.org>
To: git <git@vger.kernel.org>
Subject: Storing (hidden) per-commit metadata
Date: Fri, 19 Feb 2010 18:11:25 +0100	[thread overview]
Message-ID: <1266599485.29753.54.camel@ganieda> (raw)

[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]

To allow round-tripping pushes from Bazaar into Git, I'm looking for a
good place to store Bazaar semantics that can not be represented in Git
at the moment. This data should ideally be hidden from the user as much
as possible; it would e.g. contain mappings from git hashes to Bazaar
ids. 

One option would be to store it (as hg-git does) at the bottom of each
git commit message. However, given the amount of data and the its kind,
it would be annoying to have it displayed by e.g. "git show" or "git
log".

Some people have suggested I use the new git notes to store this
metadata, but I haven't quite figured out how to add notes that aren't
displayed by git log/show and are still propagated along with the
revision. Is that at all possible using notes, and are they the right
thing to use here?

There also doesn't appear to be any documentation on notes in
Documentation/technical at the moment. I'm happy to contribute some if
somebody can provide pointers.

Cheers,

Jelmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2010-02-20 12:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 17:11 Jelmer Vernooij [this message]
2010-02-20 17:41 ` Storing (hidden) per-commit metadata Ben Gamari
2010-02-20 18:57   ` Avery Pennarun
2010-02-21  6:34     ` Jeff King
2010-02-21  8:49       ` Johannes Schindelin
2010-02-21  8:52         ` Jeff King
2010-02-21 12:17       ` Jelmer Vernooij
2010-02-22  5:17         ` Dmitry Potapov
2010-02-22  9:56           ` Jelmer Vernooij
2010-02-22 11:28             ` Dmitry Potapov
2010-02-22 11:59               ` Jelmer Vernooij
2010-02-22 13:08                 ` Dmitry Potapov
2010-02-22 13:44                   ` Jelmer Vernooij
2010-02-22 14:20                     ` Dmitry Potapov
2010-02-22 19:13                       ` Jelmer Vernooij
2010-02-22 14:57       ` Jelmer Vernooij
2010-02-22  5:11 ` Gabriel Filion
2010-02-22  9:49   ` Jelmer Vernooij
2010-02-22 22:13 ` "Alejandro R. Sedeño"

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=1266599485.29753.54.camel@ganieda \
    --to=jelmer@samba.org \
    --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).