From: "Andrew Berry" <email@example.com>
To: "Junio C Hamano" <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org
Subject: Re: [PATCH] docs: .gitignore parsing is to the top of the repo
Date: Tue, 06 Jul 2021 20:32:52 -0400 [thread overview]
Message-ID: <CA0F1460-CB39-45DC-8DED-13F7ABA674D1@furrypaws.ca> (raw)
On 6 Jul 2021, at 20:18, Junio C Hamano wrote:
> Junio C Hamano <email@example.com> writes:
>> Line rewrapping makes it hard to see what actually got changed,
To check, that's asked for, correct? Or is it better to do one commit
with the word changes, another to clean up the wrapping?
>> does this only move "(up to the top-level of the work tree)" around
>> without anything else, as discussed?
>> If you do "toplevel" -> "top-level" while at it, perhaps we would
>> want to correct "work tree" -> "working tree".
>> Looking better.
Yes, I realized I sent the wrong file when reviewing the sent email,
hence the followup. Aside, it's not clear to me how to send patch emails
that _also_ have not-to-be-committed notes like "oops, ignore the last".
First time contributor problems!
> Another tangent. The discovery process used for the .gitattributes
> files is identical to what is done to the .gitignore files; we may
> want to make sure that the explanation we give in our documentation
> won't cause the same confusion you are trying to avoid with this
> change. Such a fix does not have to be (and probably should not be)
> a part of this change, though.
I'm out of the office for the next week, but otherwise I'm glad to take
that on when I'm back if no one else picks it up.
next prev parent reply other threads:[~2021-07-07 0:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 22:20 [PATCH] docs: .gitignore in parents is current repo only Andrew Berry
2021-07-03 0:06 ` Junio C Hamano
2021-07-03 0:21 ` Bagas Sanjaya
2021-07-05 17:30 ` Andrew Berry
2021-07-05 19:59 ` Junio C Hamano
2021-07-05 23:50 ` Andrew Berry
2021-07-06 16:18 ` Junio C Hamano
2021-07-06 20:54 ` [PATCH] docs: .gitignore parsing is to the top of the repo Andrew Berry
2021-07-06 20:57 ` Andrew Berry
2021-07-06 21:57 ` Junio C Hamano
2021-07-07 0:18 ` Junio C Hamano
2021-07-07 0:32 ` Andrew Berry [this message]
2021-07-07 1:20 ` Junio C Hamano
2021-07-18 14:12 ` Andrew Berry
2021-07-19 18:36 ` Junio C Hamano
2021-07-06 21:55 ` Junio C Hamano
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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).