All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Philipp Marek <philipp@marek.priv.at>
Cc: <git@vger.kernel.org>
Subject: Re: [RFC] Support for arbitrary tags in commits
Date: Tue, 11 Jan 2011 13:40:50 +0100	[thread overview]
Message-ID: <201101111340.50508.trast@student.ethz.ch> (raw)
In-Reply-To: <74b0628dffbd2bc0adabe5e8b0a10960.squirrel@webmail.hitco.org>

Philipp Marek wrote:
> 
> The best way I've found (so far) is to put an additional header line in the
> commit header that references an additional blob.

This comes up every few months.  The last large discussion about this
that we had IIRC was

  http://thread.gmane.org/gmane.comp.version-control.git/138848

Can you please look through that thread and state in what way your
use-case invalidates the previous reasoning?

In particular, in what way do notes (as in git-notes(1)) fail to solve
your problem?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2011-01-11 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 12:23 [RFC] Support for arbitrary tags in commits Philipp Marek
2011-01-11 12:40 ` Thomas Rast [this message]
2011-01-11 13:48   ` Philipp Marek
2011-01-11 13:53     ` Thomas Rast

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=201101111340.50508.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=philipp@marek.priv.at \
    /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.