Re: Is there way to set git commit --date to be older than 1970 ?

Peter, You should be happy of getting the error message. Since Git 2 invalid years will default to the current year (keeping the given day and month) without warnings. -- Roberto Decurnex On Wed, Oct 29, 2014 at 4:31 PM, Junio C Hamano wrote: > Peter Vojtek writes: > >> It seems the commit d

Re: `git log relative_path_to_object` does not respect the --work-tree path

. (and I'm actually maintaining the ruby-git gem, supporting git >= 1.6 T_T) I really appreciate your feedback. Regards, -- Roberto Decurnex On Mon, Sep 29, 2014 at 5:56 PM, Jonathan Nieder wrote: > Hi Roberto, > > Roberto Eduardo Decurnex Gorosito wrote: > >> When passi

Re: `git log relative_path_to_object` does not respect the --work-tree path

on, Sep 29, 2014 at 3:06 PM, Junio C Hamano wrote: > Roberto Eduardo Decurnex Gorosito > writes: > >> ~/path$ git --work-tree=~/path/to_repo log README.md > > This does not seem to specify GIT_DIR explicitly (either with the > $GIT_DIR environment variable or the --git-dir

`git log relative_path_to_object` does not respect the --work-tree path

When passing objects to the `git log`, by just naming them or using the `--objects` option, relative paths are evaluated using the current working directory instead of the current working tree path. Even the error message is clearly wrong. "unknown revision or path not in the working tree." E