git filter branch - git ignores $GIT_AUTHOR_DATE -- is this a bug? -

-

edit: summary: git not allow dates before 1973/03/03 09:46:40 (epoch+100000000s) given in "internal date format" (seconds since epoch). allow "20110224" short form of "2011-02-24". -- this no bug: not really, not documented well. -- workaround: not rely on git internal date when cannot. -- thanks to: hobbs

hi all,

i have issues git filter-branch have tracked down git commit-tree. consider script:

#!/bin/bash # please run these commands in empty directory # (should not destroy existing repo, though. think # few dangling objects)  set -e -o pipefail  git init tree=$(git write-tree) commit=$(echo "my first commit -- tree empty" |      env git_author_date="0 +0000" git commit-tree $tree)  echo "this commit $commit:" git cat-file commit $commit

note env git_author_date="0 +0000" sets date using "git internal format" -- see git-commit-tree's manpage details -- 1970-01-01.

but output of script (the raw commit) is

tree 4b825dc642cb6eb9a060e54bf8d69288fbee4904 author jane doe <jane> 1298477214 +0100 committer jane doe <jane> 1298477214 +0100  first commit -- tree empty

now why git ignoring $git_author_date? if of significance, git --version gives git version 1.7.1.

found in git date parser code:

/*  * seconds since 1970? trigger on numbers  * more 8 digits. because don't want rule out  * numbers 20070606 yyyymmdd date.  */ if (num >= 100000000 && nodate(tm)) {

since code explicitly rejects small numbers possible unix-dates, , string doesn't parse other date format, git_author_date treated invalid , ignored entirely (and apparently, silently).

your method should work fine though long stick synthesizing commits took place after 1973. otherwise, use 1 of other date formats :)


Comments

Post a Comment

Popular posts from this blog

linux - Mailx and Gmail nss config dir -

-
i trying send mail linux command line using mailx command. can send local domain no problem want set mail send gmail account receive mail sent gmail account. after configuring mail.rc so: account gmail { set smtp=smtps://smtp.gmail.com:587 set smtp-auth=login set smtp-auth-user=username@gmail.com set smtp-auth-password=password set ssl-verify=ignore } i error: resolving host smtp.gmail.com . . . done. connecting 74.125.25.109 . . . connected. missing "nss-config-dir" variable. "/home/username/dead.letter" 11/354 . . . message not sent. after looking "nss-config-dir" here , located certn.db , keyn.db files , added mail.rc so: account gmail { set smtp=smtps://smtp.gmail.com:587 set smtp-auth=login set smtp-auth-user=username@gmail.com set smtp-auth-password=password set ssl-verify=ignore set nss-config-dir=/home/user/.mozilla/firefox/location.default } now when try send mail using command: echo "sent gmail account" | mailx -v -a
Read more

c# - Is it possible to remove an existing registration from Autofac container builder? -

-
something along lines: builder.registertype<mytype>().as<itype>(); builder.registertype<mytype2>().as<itype>(); builder.deregistertype<mytype>().as<itype>() var container = builder.build(); var types = container.resolve<ienumerable<itype>>(); assert.istrue(types.count == 1); assert.istrue(types[0].gettype == typeof(mytype2)); scenario: go through bunch of assemblies , go register types want make sure have 1 implementation of given type. need before create container. track on own nice if autofac me bit. this cannot done directly using containerbuilder , unless start on new one. mind you, having first built container should able construct new container filtering away unwanted types , reusing registrations first container. this: ... var container = builder.build(); builder = new containerbuilder(); var components = container.componentregistry.registrations .where(cr => cr.activator.limittype != typ
Read more

php - Mysql PK and FK char(36) vs int(10) -

-
i have read mysql can handle indexes , searches better if tables keys integers rather char(36) uuid's. is worth converting int(10)? note: use 1 server , have have plans use multiple databases concurrently therefore removing 1 of big reasons using uuid. our tables innodb if makes difference. thanks in advance. usually rdbms can handle integer keys pk more efficient, other datatypes. reason how build index column, yes: long dont require string (or other typed) keys, should use integers. however: char(36) , int(10) far away being equal, because int(10) much smaller, char(36). dont know, if require many different keys, should keep in mind. update, complete last paragraph: int(10) 32-bit, char(36) 36 - ^byte^ (= 288-bit). not mean, int consumes less space, means, char(36) has 4 times more different keys.
Read more