From: "Yakov Lerner" <iler.ml@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: mtimes of working files
Date: Wed, 11 Jul 2007 21:36:25 +0300 [thread overview]
Message-ID: <f36b08ee0707111136t198cf559vc85c561decf9707f@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707111902040.4516@racer.site>
On 7/11/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Wed, 11 Jul 2007, Yakov Lerner wrote:
>
> > How difficult is it to have script (or maybe existing git option) that
> > would make mtimes of all working files equal to time of last commit ?
>
> I wonder if there was a secret alien invasion three days ago, with an evil
> mental virus weapon? It seems that this question has been asked three
> times in the last three days, twice on IRC, and once here.
>
> So now, I really, really, really, (repeat that 97 more times in your head,
> please) want to know why?
>
> There must be some super uber-cool application of that, that people
> _insist_ on having it. And I do not want to be left out.
I gave you my reason on IRC, you ignored it. And you continued with
"You must defend your reason. Until you defend your reason, I do not give
you the solution, although I know it". That sounded rude. If you are *curious*,
try to speak not from position of "punishing authority", but as curious people
would normally speak.
> P.S.: I know how to do it, too. And no, it does not help to try insulting
> me (unsuccessfully), even in a private chat.
If modifying mtimes of working file breaks the git, you should have
mentioned that.
I think it does not break anything in git. If this is so you should
have said so
and to give the solution (which you said you know). I am lost in guesses
as to what makes you keep your monopolistic solution secret.
Hope I can figure it without you.
In the chat, you told me that you know the answer but won't tell me.
I have to tell you that demanding from me that I tell you why other
people asked this, and to withhold the answer on the ground that
I must mind-read them and tell you their mind ... I think this is stupid
attitude on yous part.
Yakov
next prev parent reply other threads:[~2007-07-11 18:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 15:08 mtimes of working files Yakov Lerner
2007-07-11 18:05 ` Johannes Schindelin
2007-07-11 18:36 ` Yakov Lerner [this message]
2007-07-11 18:42 ` Johannes Schindelin
2007-07-11 20:26 ` Jan Hudec
2007-07-12 7:57 ` Andy Parkins
2007-07-12 17:27 ` David Woodhouse
2007-07-13 0:37 ` Theodore Tso
2007-07-13 23:00 ` David Woodhouse
2007-07-13 23:18 ` Linus Torvalds
2007-07-13 23:46 ` David Woodhouse
2007-07-14 0:10 ` Linus Torvalds
2007-07-14 0:36 ` David Woodhouse
2007-07-14 0:44 ` J. Bruce Fields
2007-07-14 0:49 ` David Woodhouse
2007-07-14 1:29 ` Jakub Narebski
2007-07-14 13:23 ` Robin Rosenberg
2007-07-14 13:09 ` Julian Phillips
2007-07-14 22:22 ` Jan Hudec
2007-07-14 22:36 ` Julian Phillips
2007-07-15 1:46 ` Daniel Barkalow
2007-07-12 6:26 ` Eric Wong
2007-07-12 13:05 ` Randal L. Schwartz
2007-07-12 18:25 ` Eric Wong
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=f36b08ee0707111136t198cf559vc85c561decf9707f@mail.gmail.com \
--to=iler.ml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).