On Wednesday, March 11, 2020 8:56:44 PM MDT Christos Pappas wrote:
> Thank you for your answers.
FYI: the list preference is inline instead of top-posting.
> From what I can deduce, both of your suggestions require that the
> commit messages(or notes) must have some special text for which we can
> search for, which is hacky and would be different on every repository.
By "different", do you mean the mechanism, or the content of the "hashtag"
itself? I would imagine that you would expect the hashtags to be different,
and that you are concerned that they might be stored differently on each
site, maybe on one site as a note like
hashtag: awesome
and on another:
label: awesome
Is that correct?
If so, then it seems like a reasonable suggestion that some tooling be built
to potentially enforce something like that using git notes and/or commit
messages?
> What I am suggesting is something like, labels on GitHub, hashtags on
> Social-Media, or Tags in News sites. It's a well known concept so it
> will be easy to understand and use.
>
> We could initially create the concept of marks/labels/{another name}
> ('tags' is already in use by another git command) and then
> incrementally enhance the git commands to use this functionality (like
> the example I gave above, with git blame).
Right, maybe git notes is just the storage mechanism for such a feature?
-Martin
--
The Qualcomm Innovation Center, Inc. is a member of Code
Aurora Forum, hosted by The Linux Foundation
