git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christos Pappas <chrispappas99@gmail.com>
To: Martin Fick <mfick@codeaurora.org>
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 20:56:44 +0200	[thread overview]
Message-ID: <CAGa6KtQ2dQWPWxbk2MH8QJxemM8QD_O=B3aYzsP5AH-sN-7PSw@mail.gmail.com> (raw)
In-Reply-To: <2001043.V3P9HlvaID@mfick-lnx>

Thank you for your answers.

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.

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).


Στις Τετ, 11 Μαρ 2020 στις 6:00 μ.μ., ο/η Martin Fick
<mfick@codeaurora.org> έγραψε:
>
> On Wednesday, March 11, 2020 1:16:09 AM MDT Christos Pappas wrote:
> > I suggest that we should have the option to mark each commit with a
> > category name, that is not necessarily unique (like 'tags') so we
> > could have commit groups.
> > For example we could:
> > git mark {commit_id} {name}
> >
> > Then we could give special functionality to some commands based on
> > those "marks".
> > For example if we had marked a few commits with the name 'fix_typo'
> > git log --mark fix_typo. Show all the commits marked with 'fix_typo'
> > git blame --mark fix_typo Run git blame but ignore commits with 'fix_typo'
>
> Perhaps git notes could be used to do something like this?
>
> -Martin
>
> --
> The Qualcomm Innovation Center, Inc. is a member of Code
> Aurora Forum, hosted by The Linux Foundation

  reply	other threads:[~2020-03-11 18:56 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 [this message]
2020-03-11 19:31     ` Martin Fick
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGa6KtQ2dQWPWxbk2MH8QJxemM8QD_O=B3aYzsP5AH-sN-7PSw@mail.gmail.com' \
    --to=chrispappas99@gmail.com \
    --cc=annulen@yandex.ru \
    --cc=git@vger.kernel.org \
    --cc=mfick@codeaurora.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).