Re: Feature idea : notes to track status of a commit, which remotes it is shared to

Thomas Rast [off-list ref] writes:

Mildred Ki'Lya [off-list ref] writes:

quoted

The idea is to basically track automatically (in notes, either in the
notes namespace or in another namespace) which repository/remote
contains a commit. When doing git log, we'd see lines with each
commit, something like:

commit b044e6d0f1a1782820b052348ab0db314e2db3ca
Author: Myself [off-list ref]
Date:   Tue Nov 20 16:46:38 2012 +0100

    This is the commit description

Published on:
    origin
    git@git.host.com:pub/repo.git

The problem here is that doing this in notes is unreliable: you'd have
to identify all places where the set of "publishes" can change for any
commit, and update them there.

Unreliable you can fix with effort.

But I think a bigger problem is that it is a pointless "false
economy" to attempt to record and try to maintain this note for each
and every commit.

When you push out a tip of the branch to a new location, you would
have to update notes to all commits from that tip down to where in
the history to record that new location?  To the root?  Also your
upstream may fetch from your published place and you may fetch it
back (you will notice that now the commit appears in your 'origin').
Would you do the traversal and update all notes?

It is both much easier and cheaper to compute this on demand as you
pointed out.