From: Jeff Carr <jcarr@linuxmachines.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git-ls-new-files & make patch, pull, etc.
Date: Tue, 06 Sep 2005 13:42:24 -0700 [thread overview]
Message-ID: <431DFF30.7010009@linuxmachines.com> (raw)
In-Reply-To: <7v1x4lz118.fsf@assigned-by-dhcp.cox.net>
On 08/22/2005 10:15 PM, Junio C Hamano wrote:
> Jeff Carr <jcarr@linuxmachines.com> writes:
>
>
>>Something simple like the perl script at the bottom would be useful for
>>showing files that haven't been added via git-update-cache --add already.
>
>
> If I am not mistaken, you just reinvented:
>
> $ git ls-files --others
>
> in a very expensive way. Notice your `find . -type f` that does
> not prune .git directory upfront.
>
> Also you may want to take a look at:
>
> $ git ls-files --others --exclude-from=.git/info/exclude
Yes, you are right -- I did reinvent the above poorly :)
I also was using a perl script to parse the output of git-whatchanged to
set the datestamps on the files to the last modified time. If I remember
correctly, there was some threads at the beginning of git about how
datestamps were not accurate so there was no point in setting them(?) Or
maybe I mis-understood. In any case, sometimes it is useful for me
because I just want to look at what files I changed today or yesterday
or something to that effect. Sometimes in the kernel/Documentation
directories it is useful because you can see what documentation was
done/changed this year. Sometimes that's nice if you are looking for new
things you might not know much about; recently I was digging around in
the I2C stuff to try to figure out if I could read the right temperature
sensor on the smbus on a machine. Anyway, I'll just use that but perhaps
there is also a "correct" way to keep timestamps?
BTW, for what it's worth, you can't package git under debian sarge
because asciidoc doesn't support "-b xhtml11". I pulled it from sid and
it packaged it fine. Just an FYI. I emailed the asciidoc maintainer for
what it's worth.
Thanks a lot,
Jeff
next prev parent reply other threads:[~2005-09-06 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 2:07 git-ls-new-files & make patch, pull, etc Jeff Carr
2005-08-23 5:15 ` Junio C Hamano
2005-09-06 20:42 ` Jeff Carr [this message]
2005-09-06 21:08 ` Junio C Hamano
2005-09-08 22:19 ` Jeff Carr
2005-09-09 3:19 ` Junio C Hamano
2005-08-23 6:48 ` Johannes Schindelin
2005-09-06 19:06 ` Jeff Carr
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=431DFF30.7010009@linuxmachines.com \
--to=jcarr@linuxmachines.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).