git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Jacobs <b@q3q.us>
To: git@vger.kernel.org
Subject: git-subtree with log.date=relative
Date: Sun, 19 Jul 2015 20:03:50 -0400	[thread overview]
Message-ID: <20150719200350.10ae4534@q3q.us> (raw)

[-- Attachment #1: Type: text/plain, Size: 529 bytes --]

Dear git Developers,

When setting log.date=relative in ~/.gitconfig, all "git subtree push"
commands fail with errors like this:

git push using:  ../../repos/second master
fatal: invalid date format: 8 minutes ago
Can't copy commit 10827bbf18aa17108e07039d9c125000889a4365

I believe git subtree is making a call to git log and relying on the
dates in the output being machine-readable instead of human-readable.
It should pass --date=default if it wants to ensure the default date
format is used.

Bryan Jacobs

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2015-07-20  0:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150719200350.10ae4534@q3q.us \
    --to=b@q3q.us \
    --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).