From: Jakub Narebski <jnareb@gmail.com>
To: "Etienne Vallette d'Osia" <dohzya@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: Improve tags
Date: Fri, 27 Mar 2009 07:15:42 -0700 (PDT) [thread overview]
Message-ID: <m3bprn2gs7.fsf@localhost.localdomain> (raw)
In-Reply-To: <49CCAAD3.4070104@gmail.com>
"Etienne Vallette d'Osia" <dohzya@gmail.com> writes:
> > You described your motivation and use case very clearly!
> >
> > Maybe "label" would be an appropriate name for "non-unique tags". I
> > assume they should be local and non-versioned. It sounds as if a file
> > storing a list of sha1s could be the simplest approach (one file per
> > label in a new subdir of .git), although this may not scale well. A
> > first step could be implementing a command "git label" in shell which
> > sets and displays labels. Later on, various builtins would need to be
> > taught about it if you want labels displayed in log etc.
>
> Thanks a lot
>
> "label" is perfect !
>
> In fact, I was thinking about non-local labels.
> But keeping information in a separate file and not in commit directly
> is a very nice idea (and closer than the current tag implementation).
> I love your approach, you have just make this idea realizable
This is a bit argument for (abandoned / dropped) 'notes' commit header
idea... But only a tiny bit.
More seriously: take a look at 'notes' idea; I'm not sure what state
they are currently, but they are in active (more or less) development.
They are extension of tags, allowing post-fact annotation of commits.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-03-27 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 12:48 Improve tags Etienne Vallette d'Osia
2009-03-26 16:02 ` Michael J Gruber
2009-03-27 10:30 ` Etienne Vallette d'Osia
2009-03-27 14:15 ` Jakub Narebski [this message]
2009-03-27 14:39 ` Etienne Vallette d'Osia
2009-03-26 21:53 ` Nanako Shiraishi
2009-03-27 10:05 ` Etienne Vallette d'Osia
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=m3bprn2gs7.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=dohzya@gmail.com \
--cc=git@drmicha.warpmail.net \
--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 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).