From: Paul Lalonde <paul.a.lalonde@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: Git usage
Date: Sun, 12 Jan 2025 14:50:18 -0800 [thread overview]
Message-ID: <CA+POUVitQP81KooM64CnwDNMbXJaqQrWurNHjPW+4RReJHF_kg@mail.gmail.com> (raw)
In-Reply-To: <D70FY5JO6NNF.3BX4A457NUZFY@pixelhero.dev>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
Nice, I can kind of make it work for me:
fluxcpu% git/query -c 'dcc6924f24d885f48456a99575ac6619a8df9d45^^
61ce30435cd176e5967de641527656239db1e952'
@ sys/src/nix/k10/k8cpu
@ sys/src/nix/k10/l32p.s
Does the @ at the start of the lines have any significance?
Paul
On Sun, Jan 12, 2025 at 2:20 PM Noam Preil <noam@pixelhero.dev> wrote:
> There is, qit/query has a flag for it.
>
> We're currently using git/walk to fetch them - oh! We should only need
> to diff _modified_ files, whereas we currently also diff files which are
> _added_ or _removed_ as well, iirc.
>
> I'm currently setting up my replacement 9front system, I'll take a look
> shortly!
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc30944502958e1a0-M281a92d5336c7d089d6ddf36
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2342 bytes --]
next prev parent reply other threads:[~2025-01-12 22:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 19:55 [9fans] " Paul Lalonde
2025-01-12 20:10 ` Ron Minnich
2025-01-12 20:44 ` Christopher Nielsen
2025-01-12 21:06 ` [9fans] " Paul Lalonde
2025-01-12 21:55 ` Noam Preil
2025-01-12 22:08 ` Paul Lalonde
2025-01-12 22:17 ` Noam Preil
2025-01-12 22:50 ` Paul Lalonde [this message]
2025-01-13 0:07 ` ori
2025-01-13 0:14 ` Paul Lalonde
2025-01-13 0:34 ` ori
2025-01-13 0:32 ` ori
2025-01-13 2:22 ` Paul Lalonde
2025-01-13 5:55 ` ori
2025-01-13 5:59 ` ori
2025-01-13 7:46 ` Michael Forney
2025-01-13 0:17 ` [9fans] " ori
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=CA+POUVitQP81KooM64CnwDNMbXJaqQrWurNHjPW+4RReJHF_kg@mail.gmail.com \
--to=paul.a.lalonde@gmail.com \
--cc=9fans@9fans.net \
/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).