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 14:53:08 +0100 [thread overview]
Message-ID: <201101111453.08178.trast@student.ethz.ch> (raw)
In-Reply-To: <edec2e42a531b00ffd6a2689095460d5.squirrel@webmail.hitco.org>
Philipp Marek wrote:
> > In particular, in what way do notes (as in git-notes(1)) fail to solve
> > your problem?
> Well, my biggest concerns are that users might trash them, and that they are
> voided by amend, rebase etc. (which I tried to address by collecting header
> lines).
They aren't lost any more (since 1.7.1) if you properly configure
notes.rewriteRef.
--
Thomas Rast
trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2011-01-11 13:53 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
2011-01-11 13:48 ` Philipp Marek
2011-01-11 13:53 ` Thomas Rast [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=201101111453.08178.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 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).