git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Stefan Beller <sbeller@google.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Elijah Newren <newren@gmail.com>, Git Mailing list <git@vger.kernel.org>
Subject: Re: which files are "known to git"?
Date: Mon, 21 May 2018 11:15:57 -0700	[thread overview]
Message-ID: <CAGZ79kZ7_QJk7BaZ2R7W=9fvNtbyeM9O9qvXdPcHsUXgD=93Aw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1805211335250.21160@localhost.localdomain>

On Mon, May 21, 2018 at 10:40 AM, Robert P. J. Day
<rpjday@crashcourse.ca> wrote:
> On Mon, 21 May 2018, Elijah Newren wrote:
>
>> Hi Robert,
>>
>> I had always assumed prior to your email that 'known to Git' meant
>> 'tracked' or 'recorded in the index'...
>
>   i *know* i've been in this discussion before,

https://public-inbox.org/git/alpine.LFD.2.21.1711120430580.30032@localhost.localdomain/

via

git clone --mirror https://public-inbox.org/git git-ml && cd git-ml
git log --oneline --author=rpjday@crashcourse.ca
/ known # search for "known" in message subjects

I really value the public inbox to work as a git repo, as then you
can dig though it just as you dig through commits.

      parent reply	other threads:[~2018-05-21 18:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 11:18 which files are "known to git"? Robert P. J. Day
2018-05-21 13:58 ` Randall S. Becker
2018-05-21 15:09 ` Elijah Newren
2018-05-21 15:18   ` Duy Nguyen
2018-05-21 15:49   ` Robert P. J. Day
2018-05-21 15:53   ` Robert P. J. Day
2018-05-21 16:08   ` Junio C Hamano
2018-05-21 17:40   ` Robert P. J. Day
2018-05-21 17:53     ` Jonathan Nieder
2018-05-21 18:09       ` Robert P. J. Day
2018-05-21 18:15         ` Jonathan Nieder
2018-05-22  2:14       ` Junio C Hamano
2018-05-23  8:20       ` Robert P. J. Day
2018-05-21 18:13     ` Elijah Newren
2018-05-21 18:14       ` Robert P. J. Day
2018-05-21 18:15     ` Stefan Beller [this message]

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

  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 \
    --in-reply-to='CAGZ79kZ7_QJk7BaZ2R7W=9fvNtbyeM9O9qvXdPcHsUXgD=93Aw@mail.gmail.com' \
    --to=sbeller@google.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    --cc=rpjday@crashcourse.ca \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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