From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Recording the date at which a change was pushed to Savannah
Date: Wed, 03 Dec 2014 09:35:16 +0100 [thread overview]
Message-ID: <87388xw2pn.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87r3whkw6w.fsf@uwakimon.sk.tsukuba.ac.jp
"Stephen J. Turnbull" <stephen@xemacs.org> writes:
> Glenn Morris writes:
>
> > Obviously the same sort of [commit date/push date lag] will apply
> > if someone delays pushing their local commits to Savannah. Or the
> > next time a long-lived feature branch gets merged to master.
>
> As I wrote before, I think it's reasonable to want to know when a
> commit was pushed.
This is a distributed version control system. I can push a branch from
my own repository to repository C, make a pull request for the owner of
repository D, they merge their own branches into the respective results
and push to different branches in the "main" repository where the
branches are eventually merged.
So when was that commit pushed into the upstream repository? You are
likely looking for something akin to the file creation date of the
object blob in the "upstream" repository. That's sort of the thing one
might expect to be stored in the ephemeral reflog but it turns out it
isn't.
It's also a very shaky piece of information and must not be part of the
commit itself because then it would change the commit id. And it really
makes only sense repository-locally. And it's not like one can access
the reflog of a remote repository either.
So "when a commit was pushed" rather than "committed/created" is
information that cannot sensibly be maintained in distributed version
control systems and workflows with a commit identity in some readily
available form since it is, by its nature, repository-local and thus not
available for anybody not having local access to the main repository.
--
David Kastrup
next prev parent reply other threads:[~2014-12-03 8:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 2:55 Recording the date at which a change was pushed to Savannah Glenn Morris
2014-12-02 4:55 ` Yuri Khan
2014-12-02 5:05 ` Stephen J. Turnbull
2014-12-02 13:48 ` Stefan Monnier
2014-12-03 6:22 ` Glenn Morris
2014-12-03 6:47 ` David Kastrup
2014-12-03 7:51 ` Stephen J. Turnbull
2014-12-03 8:35 ` David Kastrup [this message]
2014-12-03 9:50 ` Stephen J. Turnbull
2014-12-03 10:04 ` David Kastrup
2014-12-03 14:18 ` Stefan Monnier
2014-12-03 16:19 ` Yuri Khan
2014-12-03 18:59 ` Stefan Monnier
2014-12-03 18:02 ` Eli Zaretskii
2014-12-03 19:00 ` Stefan Monnier
2014-12-03 19:06 ` Eli Zaretskii
2014-12-03 19:34 ` Stefan Monnier
2014-12-03 20:24 ` Eli Zaretskii
2014-12-03 21:10 ` Stefan Monnier
2014-12-04 2:52 ` Yuri Khan
2014-12-04 6:17 ` Eli Zaretskii
2014-12-04 2:58 ` Glenn Morris
2014-12-04 3:57 ` Stefan Monnier
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=87388xw2pn.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.