From: Martin Fick <mfick@codeaurora.org>
To: Christos Pappas <chrispappas99@gmail.com>
Cc: git@vger.kernel.org, annulen@yandex.ru
Subject: Re: [Feature request] Give non-unique names to commits for grouping
Date: Wed, 11 Mar 2020 13:31:41 -0600 [thread overview]
Message-ID: <12099923.Cjvj2aPIT9@mfick-lnx> (raw)
In-Reply-To: <CAGa6KtQ2dQWPWxbk2MH8QJxemM8QD_O=B3aYzsP5AH-sN-7PSw@mail.gmail.com>
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
next prev parent reply other threads:[~2020-03-11 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 23:16 [Feature request] Give non-unique names to commits for grouping Christos Pappas
2020-03-10 23:21 ` Konstantin Tokarev
2020-03-11 16:00 ` Martin Fick
2020-03-11 18:56 ` Christos Pappas
2020-03-11 19:31 ` Martin Fick [this message]
2020-03-11 20:47 ` Christos Pappas
2020-03-11 20:04 ` Junio C Hamano
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=12099923.Cjvj2aPIT9@mfick-lnx \
--to=mfick@codeaurora.org \
--cc=annulen@yandex.ru \
--cc=chrispappas99@gmail.com \
--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 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.