On Thu, 12 Oct 2017, Jeff King wrote:
> On Fri, Oct 13, 2017 at 01:18:00AM +0200, Johannes Schindelin wrote:
>
> > [who I had to cull from the To:/Cc: headers, as my mailer consistently
> > told me that there is no valid DNS record to route mail to
> > rpj...@crashcourse.ca, which *is* weird.]
>
On Fri, Oct 13, 2017 at 01:18:00AM +0200, Johannes Schindelin wrote:
> [who I had to cull from the To:/Cc: headers, as my mailer consistently
> told me that there is no valid DNS record to route mail to
> rpj...@crashcourse.ca, which *is* weird.]
You are not the only one to mention this, so I
Hi Robert,
[who I had to cull from the To:/Cc: headers, as my mailer consistently
told me that there is no valid DNS record to route mail to
rpj...@crashcourse.ca, which *is* weird.]
On Fri, 6 Oct 2017, Robert P. J. Day wrote:
> On Fri, 6 Oct 2017, Junio C Hamano wrote:
>
> > Don't waste time
> rpj...@crashcourse.ca:
> but even that isn't a really compelling reason. so what's it for?
I use it to ignore stuff in my git-versioned home directory.
Every time I use a new program and it creates a config file or a config
directory, it shows up as clutter in magit in my git versioned
On Fri, Oct 06, 2017 at 01:39:16PM -0400, Robert P. J. Day wrote:
> On Fri, 6 Oct 2017, Junio C Hamano wrote:
> > This is primarily why .git/info/exclude exists. A user who does not
> > use the same set of tools to work on different projects may not be
> > able to use ~/.gitconfig with
Hi,
Robert P. J. Day wrote:
> On Fri, 6 Oct 2017, Junio C Hamano wrote:
>> Don't waste time by seeking a "compelling" reason. A mere "this is
>> the most expedite way to gain convenience" back when something was
>> introduced could be an answer, and it is way too late to complain
>> about such
On Fri, 6 Oct 2017, Junio C Hamano wrote:
> rpj...@crashcourse.ca writes:
>
> > at the other end, users are certainly welcome to add extra
> > patterns to be ignored, based purely on the way they work --
> > perhaps based on their choice of editor, they might want to
> > exclude *.swp files, or
On Fri, 2017-10-06 at 06:14 -0400, rpj...@crashcourse.ca wrote:
>and in this funny grey area in between, we have .git/info/exclude,
> to be used for ... what, exactly? the one argument i've come up with
> is the situation where you discover that a repo you've cloned has an
> incomplete set of
rpj...@crashcourse.ca writes:
> at the other end, users are certainly welcome to add extra patterns
> to be ignored, based purely on the way they work -- perhaps based on
> their choice of editor, they might want to exclude *.swp files, or
> if working on a Mac, ignore .DS_Store, and so on,
currently having a discussion with ben straub of "pro git" notoriety,
and he and i seem to agree that there's not much value in registering
ignore patterns in a repo-specific .git/info/exclude file.
on the one hand, the .gitignore files that come with a repo would
represent (in ben's
10 matches
Mail list logo
