From: Ori Bernstein <ori@eigenstate.org>
To: 9front@9front.org
Cc: Jens Staal <staal1978@gmail.com>
Subject: Re: [9front] drawterm: add .gitignore
Date: Wed, 22 May 2024 13:25:02 -0400 [thread overview]
Message-ID: <20240522132502.318b38d5ec41605ce7d1e600@eigenstate.org> (raw)
In-Reply-To: <CAK8RtFqg=9ZcQH2fy4qmgFg_hhkt2v1vM_a9jX-QHyJBjsBYAQ@mail.gmail.com>
Git9 doesn't do anything with untracked files,
and therefore doesn't need a gitignore.
On Wed, 22 May 2024 19:12:40 +0200
Jens Staal <staal1978@gmail.com> wrote:
> Does **.a work on git9 too to exclude in all directories?
>
> Den ons 22 maj 2024 18:55Jacob Moody <moody@posixcafe.org> skrev:
>
> > On 5/22/24 11:33, Romano wrote:
> > > Thanks sirjofri, I forgot about that repo-specific
> > > configuration and I'll use that.
> > >
> > > I don't know why generally /drawterm and *.[ao]
> > > would ever be wanted to be viewed in this
> > > specific repo when doing `git diff`, but the
> > > .git/info/exclude works for me.
> >
> > The repo must be pushed to with git9 because
> > write is only available from hjgit://
> > This means that most people developing
> > drawterm are doing so from the comfort
> > of git9 which does not have this issue.
> >
> > Your .gitignore is also wrong, you would
> > want to exclude the .o and .a files in the
> > subdirectories as well.
> >
> >
--
Ori Bernstein <ori@eigenstate.org>
next prev parent reply other threads:[~2024-05-22 17:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 23:33 Romano
2024-05-22 9:43 ` sirjofri
2024-05-22 12:07 ` [9front] Tomás Ciccola
2024-05-22 16:33 ` [9front] drawterm: add .gitignore Romano
2024-05-22 16:48 ` sirjofri
2024-05-22 16:52 ` Jacob Moody
2024-05-22 17:12 ` Jens Staal
2024-05-22 17:25 ` Ori Bernstein [this message]
2024-05-22 17:45 ` Romano
2024-05-23 2:03 ` ori
2024-05-22 17:40 ` Romano
2024-05-22 17:46 ` Jacob Moody
2024-05-22 18:10 ` Romano
2024-05-22 19:39 ` Jacob Moody
2024-05-22 21:01 ` Jacob Moody
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=20240522132502.318b38d5ec41605ce7d1e600@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=staal1978@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).