git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Konstantin Tokarev <annulen@yandex.ru>
To: Christos Pappas <chrispappas99@gmail.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [Feature request] Give non-unique names to commits for grouping
Date: Wed, 11 Mar 2020 02:21:11 +0300	[thread overview]
Message-ID: <6552181583882319@iva1-398527a32f9a.qloud-c.yandex.net> (raw)
In-Reply-To: <CAGa6KtSgGOLVjHdubwRW=Bvnjnp2PoP7jJ5_NxNWGFLrVYT9SA@mail.gmail.com>



11.03.2020, 02:16, "Christos Pappas" <chrispappas99@gmail.com>:
> Dear Git users,
>
> 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'

Why not use git log --grep? It can give better results if someone accidentally
forgets to use mark properly, but mentions keyword in the topic.

That said, it would be great if there was an easy way to use git log --grep
with commit topics only (i.e., search only in the first line)

-- 
Regards,
Konstantin


  reply	other threads:[~2020-03-10 23:21 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 [this message]
2020-03-11 16:00 ` Martin Fick
2020-03-11 18:56   ` Christos Pappas
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=6552181583882319@iva1-398527a32f9a.qloud-c.yandex.net \
    --to=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.
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).