From: Jed Brown <jed@59A2.org>
To: John Keeping <john@keeping.me.uk>, David Kastrup <dak@gnu.org>
Cc: Duy Nguyen <pclouds@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Creating own hierarchies under $GITDIR/refs ?
Date: Sun, 02 Feb 2014 16:44:56 -0700 [thread overview]
Message-ID: <878utt84g7.fsf@jedbrown.org> (raw)
In-Reply-To: <20140202122432.GC29976@serenity.lan>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
John Keeping <john@keeping.me.uk> writes:
> I actually wonder if you could do this with notes and git-grep; for
> example:
>
> git grep -l keeping.me.uk refs/notes/amlog |
> sed -e 's/.*://' -e 's!/!!g'
>
> That should be relatively efficient since you're only looking at the
> current notes tree.
I added notes handling to gitifyhg and would search it similar to this.
Since gitifyhg is two-way, I could not modify the commits. Later, when
we converted several repositories (up to 50k commits/80 MB), I appended
Hg-commit: $Hg_commit_hash
to all the commit messages. This way it shows up on the web interface,
users don't have to obtain the notes specially, and "git log --grep"
works naturally. I think it's worth considering this simple solution;
existing Git users won't mind recloning once.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2014-02-02 23:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 10:37 Creating own hierarchies under $GITDIR/refs ? David Kastrup
2014-02-02 11:00 ` Duy Nguyen
2014-02-02 11:19 ` David Kastrup
2014-02-02 11:31 ` John Keeping
2014-02-02 11:42 ` David Kastrup
2014-02-02 12:24 ` John Keeping
2014-02-02 23:44 ` Jed Brown [this message]
2014-02-02 12:00 ` Duy Nguyen
2014-02-02 12:09 ` David Kastrup
2014-02-02 11:04 ` Andreas Schwab
2014-02-02 23:26 ` Jeff King
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=878utt84g7.fsf@jedbrown.org \
--to=jed@59a2.org \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=pclouds@gmail.com \
/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).