git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Lin Terry <terrylin.developer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: I can do past and feature commits. It is a bug?
Date: Mon, 9 Jul 2018 17:02:43 -0700	[thread overview]
Message-ID: <20180710000243.GK14196@aiede.svl.corp.google.com> (raw)
In-Reply-To: <CACNAd2RB4GqfrfbqViX5Jwtpcsm64uQ2uU4K4W+AVR0y5d96gA@mail.gmail.com>

+the public git mailing list, git-security@googlegroups.com -> bcc
Hi,

Lin Terry wrote:

> I can do past and feature commits. It is a bug?
>
> Check out my gitgub page.
> https://github.com/terrylinooo
>
> You can see a LOVE, they are past commits I commited yesterday.

The ability to set the author and committer date freely is an
intentional capability.  See the 'Commit Information' section of "git
help commit-tree", for example.

If you'd like the ability to prove that an object was pushed by a
particular person at a particular time, you might like the push
certificates feature.  The pusher is authenticated using a GPG
signature; the push time can be recorded by the server in its
pre-receive or post-receive hook (so you still have to trust the
server for that).  See the description of --signed in "git help push"
and of hooks in "git help receive-pack" for more details on that
subject.

Thanks and hope that helps,
Jonathan

           reply	other threads:[~2018-07-10  0:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CACNAd2RB4GqfrfbqViX5Jwtpcsm64uQ2uU4K4W+AVR0y5d96gA@mail.gmail.com>]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180710000243.GK14196@aiede.svl.corp.google.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=terrylin.developer@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).