From: "Philipp Marek" <philipp@marek.priv.at>
To: "Thomas Rast" <trast@student.ethz.ch>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Support for arbitrary tags in commits
Date: Tue, 11 Jan 2011 14:48:59 +0100 (CET) [thread overview]
Message-ID: <edec2e42a531b00ffd6a2689095460d5.squirrel@webmail.hitco.org> (raw)
In-Reply-To: <201101111340.50508.trast@student.ethz.ch>
Hello Thomas,
thank you very much for the quick answer.
>> 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?
Thank you, just reading it.
> 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).
Well, from this thread I suppose the "best" (or at least easiest) way forward
is to use notes, if necessary.
Thank you!
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
next prev parent reply other threads:[~2011-01-11 13:49 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 [this message]
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=edec2e42a531b00ffd6a2689095460d5.squirrel@webmail.hitco.org \
--to=philipp@marek.priv.at \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/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).