Junio C Hamano writes:
> Imagine this scenario:
>
> - Contributor A writes a change on 2017-07-01 and send it in to me
> - Contributor B writes a change on 2017-07-03 and send it in to me
> - I apply change from B on 2017-07-04 on 'master'
> - I apply change from A on 2017-07-05 on 'master'
>
Todd Lewis writes:
> Trying not to sound snide, but, what's the point of "--date=" on commits if
> you
> can't use it later? Granted, things always seem harder until you understand
> how
> the work. Thanks again.
You do not sound snide at all, at least to me ;-)
Imagine this scenario:
- Con
On 07/06/2017 12:22 PM, Junio C Hamano wrote:
> If you didn't create this repository back in 2012, then the syntax
> "master@{01-01-2012}" that asks "Back at the beginning of 2012, what
> object did the master branch point at?" does not have a sensible
> answer. That can be seen in the warning y
Todd Lewis writes:
> [utoddl@tarna gitbug]$ git diff master@{01-01-2012} charter.txt
> warning: Log for 'master' only goes back to Thu, 6 Jul 2017 08:19:45 -0400.
What you observed is how @{} syntax is designed to
work, and is not limited to "git diff". Any Git command e.g. "git
rev-parse maste
I've run into what I think is a bug wrt date handling in "git diff". I have some
historical data with which I'm attempting to populate a new git repo with
back-dated commits. That appears to work. But referencing those commits by date
with "git diff" does not. (I have no idea if the problem is limi
5 matches
Mail list logo
