On 09/06/2005 02:08 PM, Junio C Hamano wrote:
Jeff Carr [EMAIL PROTECTED] writes:
... 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.
The point of those
In my opinion, setting the file timestamp to the commit time (or
any other time other than the time of checkout) tends to screw
you up more than help you.
Suppose you have the latest checked out in your working tree,
you build and test, and find regressions. You'd want to check
out from an older
On 08/22/2005 10:15 PM, Junio C Hamano wrote:
Jeff Carr [EMAIL PROTECTED] 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
Jeff Carr [EMAIL PROTECTED] writes:
... 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.
The point of those thread was that clocks on machines tend to be
not so
Hi,
On Mon, 22 Aug 2005, Jeff Carr wrote:
patch:
git-diff-files -p
git diff
push:
git-send-pack `cat .git/branches/origin`
git push origin (or maybe git push HEAD:origin)
pull:
git-pull-script `cat .git/branches/origin`
git-read-tree -m HEAD
Jeff Carr [EMAIL PROTECTED] 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
6 matches
Mail list logo
