From: wolf <wolf@wolfsden.cz>
To: "mhrunnels@yahoo.com" <mhrunnels@yahoo.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: How To Search Git Tree?
Date: Fri, 28 Apr 2023 00:29:56 +0200 [thread overview]
Message-ID: <ZEr3ZHtIe4xFNaWk@ws> (raw)
In-Reply-To: <254875562.615797.1682634270914@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On 2023-04-27 22:24:30 +0000, mhrunnels@yahoo.com wrote:
> The https://git.savannah.gnu.org/cgit/guix.git/tree/ is a great resource for exploring the Guix source code.
>
> However, manually traversing the tree is cumbersome and slow.
>
> Is there a method or technique or tool for searching the git tree?
>
> All suggestions appreciated.
I'm not sure about savannah, but I would recommend just cloning the
repository. Then you will have all your tools available.
>
> MH
>
>
W.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-04-27 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <254875562.615797.1682634270914.ref@mail.yahoo.com>
2023-04-27 22:24 ` How To Search Git Tree? mhrunnels
2023-04-27 22:29 ` wolf [this message]
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZEr3ZHtIe4xFNaWk@ws \
--to=wolf@wolfsden.cz \
--cc=help-guix@gnu.org \
--cc=mhrunnels@yahoo.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 read-only IMAP folder(s) and NNTP newsgroup(s).