[9front] drawterm: add .gitignore

[9front] drawterm: add .gitignore

[Romano]

When I build drawterm on Mac OSX I get a lot of
untracked files listed (e.g., *.[ao]). Could a
.gitignore be added to ignore those files?

commit a3b5694689a42acb0b9b0bd1fdcbe633d6a6c72f (HEAD -> front)
Author: Romano <me+git@fallglow.com>
Date:   Tue May 21 16:25:41 2024 -0700

    Add .gitignore

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..90ec42c
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,2 @@
+*.[ao]
+drawterm

Re: [9front] drawterm: add .gitignore

[sirjofri]

mv .gitignore .git/info/exclude

22.05.2024 01:41:27 Romano <me+unobe@fallglow.com>:

>
> When I build drawterm on Mac OSX I get a lot of
> untracked files listed (e.g., *.[ao]). Could a
> .gitignore be added to ignore those files?
>
> commit a3b5694689a42acb0b9b0bd1fdcbe633d6a6c72f (HEAD -> front)
> Author: Romano <me+git@fallglow.com>
> Date:   Tue May 21 16:25:41 2024 -0700
>
>     Add .gitignore
>
> diff --git a/.gitignore b/.gitignore
> new file mode 100644
> index 0000000..90ec42c
> --- /dev/null
> +++ b/.gitignore
> @@ -0,0 +1,2 @@
> +*.[ao]
> +drawterm

[9front]

[Tomás Ciccola]

unsubscribe

Re: [9front] drawterm: add .gitignore

[Romano]

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.

Re: [9front] drawterm: add .gitignore

[sirjofri]

22.05.2024 18:34:51 Romano <me+unobe@fallglow.com>:

> 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.

There are people who strictly say that something like a .gitignore shouldn't be part of the repo. I don't know about the drawterm maintainers, but .git/info/exclude works. I think you could also add the .gitignore to the .gitignore and just not commit it. But my memory of git on unices is fading.

sirjofri

Re: [9front] drawterm: add .gitignore

[Jacob Moody]

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.

Re: [9front] drawterm: add .gitignore

[Jens Staal]

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

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.
>
>

[-- Attachment #2: Type: text/html, Size: 1121 bytes --]

Re: [9front] drawterm: add .gitignore

[Ori Bernstein]

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>

Re: [9front] drawterm: add .gitignore

[Romano]

On Wed May 22 10:16:06 -0700 2024, staal1978@gmail.com wrote:
> Does **.a work on git9 too to exclude in all directories?

** have a special meaning and shouldn't be needed for stock
git (see my previous reply which refers to the git
documentation), but as Ori mentioned git9 doesn't suffer
from this.

Re: [9front] drawterm: add .gitignore

[ori]

Quoth Romano <me+unobe@fallglow.com>:
> 
> On Wed May 22 10:16:06 -0700 2024, staal1978@gmail.com wrote:
> > Does **.a work on git9 too to exclude in all directories?
> 
> ** have a special meaning and shouldn't be needed for stock
> git (see my previous reply which refers to the git
> documentation), but as Ori mentioned git9 doesn't suffer
> from this.

for the record -- I don't really hack on drawterm, and when
I do, I'm committing from 9front; that said, I don't think
it hurts anything to have a .gititnore for the people doing
hacking on it from unix.

so, basically, I don't care.

Re: [9front] drawterm: add .gitignore

[Romano]

On Wed May 22 09:53:50 -0700 2024, moody@posixcafe.org wrote:
> Your .gitignore is also wrong, you would
> want to exclude the .o and .a files in the
> subdirectories as well.

Why do you think it's wrong? As written, it applies to all
subdirectories. This is how it works on the version of git
( version 2.32.1 (Apple Git-133) ) I tested against and
aligns with the documentation for git:
https://git-scm.com/docs/gitignore . See the 'EXAMPLES'
section.

Re: [9front] drawterm: add .gitignore

[Jacob Moody]

On 5/22/24 12:40, Romano wrote:
> On Wed May 22 09:53:50 -0700 2024, moody@posixcafe.org wrote:
>> Your .gitignore is also wrong, you would
>> want to exclude the .o and .a files in the
>> subdirectories as well.
> 
> Why do you think it's wrong? As written, it applies to all
> subdirectories. This is how it works on the version of git
> ( version 2.32.1 (Apple Git-133) ) I tested against and
> aligns with the documentation for git:
> https://git-scm.com/docs/gitignore . See the 'EXAMPLES'
> section.

I misplaced my understanding of which syntax is recursive or
not. So yes this is .gitignore will work as advertised.

I'm still not interested in it for the other reasons stated.

Re: [9front] drawterm: add .gitignore

[Romano]

On Wed May 22 10:52:45 -0700 2024, moody@posixcafe.org wrote:
> I'm still not interested in it for the other reasons stated.

Oh, I'm sorry, I didn't reply directly to the other part of
your message because I didn't want you to think that I was
pushing back against that reason for inclusion of the patch.
The reason you stated re: who develops and with what makes
sense, and I didn't think there was anything more to be said
about that.

I restricted my reply to your statement about the format
of gitignore.

Re: [9front] drawterm: add .gitignore

[Jacob Moody]

On 5/22/24 13:10, Romano wrote:
> On Wed May 22 10:52:45 -0700 2024, moody@posixcafe.org wrote:
>> I'm still not interested in it for the other reasons stated.
> 
> Oh, I'm sorry, I didn't reply directly to the other part of
> your message because I didn't want you to think that I was
> pushing back against that reason for inclusion of the patch.
> The reason you stated re: who develops and with what makes
> sense, and I didn't think there was anything more to be said
> about that.
> 
> I restricted my reply to your statement about the format
> of gitignore.

Look, there are clearly some rough feelings from our other discussion.
I am not trying to tone police and dictate strict rules for how people need to talk here.
I was at the time just trying to explain why I got frustrated with how the conversation had gone.
Part of that was communicating how I had interpreted your mail at the time, and trying to explain what I
think the etiquette is for how conversations and discussions should go here.
I should also mention that I am not the rule maker here, I am simply speaking from my experience of how
others have traditionally got along. If I am wrong I hope someone would mention their own idea of how
these things should go.

I don't want to turn every discussion in to this.
So I will try to abstain from further discussions of your patches.

Thanks,
moody

Re: [9front] drawterm: add .gitignore

[Jacob Moody]

On 5/22/24 14:39, Jacob Moody wrote:
> On 5/22/24 13:10, Romano wrote:
>> On Wed May 22 10:52:45 -0700 2024, moody@posixcafe.org wrote:
>>> I'm still not interested in it for the other reasons stated.
>>
>> Oh, I'm sorry, I didn't reply directly to the other part of
>> your message because I didn't want you to think that I was
>> pushing back against that reason for inclusion of the patch.
>> The reason you stated re: who develops and with what makes
>> sense, and I didn't think there was anything more to be said
>> about that.
>>
>> I restricted my reply to your statement about the format
>> of gitignore.
> 
> Look, there are clearly some rough feelings from our other discussion.
> I am not trying to tone police and dictate strict rules for how people need to talk here.
> I was at the time just trying to explain why I got frustrated with how the conversation had gone.
> Part of that was communicating how I had interpreted your mail at the time, and trying to explain what I
> think the etiquette is for how conversations and discussions should go here.
> I should also mention that I am not the rule maker here, I am simply speaking from my experience of how
> others have traditionally got along. If I am wrong I hope someone would mention their own idea of how
> these things should go.
> 
> I don't want to turn every discussion in to this.
> So I will try to abstain from further discussions of your patches.
> 

Unobe has clarified to me that the tone I interpreted from their last email here was not what they intended.
So my previous email may be discarded. Sorry for the noise.

- moody