git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Mildred Ki'Lya <mildred-ml@mildred.fr>
Cc: <git@vger.kernel.org>
Subject: Re: Feature idea : notes to track status of a commit, which remotes it is shared to
Date: Tue, 19 Feb 2013 11:13:19 +0100	[thread overview]
Message-ID: <87bobgtxvk.fsf@pctrast.inf.ethz.ch> (raw)
In-Reply-To: <51234801.5050208@mildred.fr> (Mildred Ki'Lya's message of "Tue, 19 Feb 2013 10:38:09 +0100")

Mildred Ki'Lya <mildred-ml@mildred.fr> writes:

> 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 <myself@localhost.localdomain>
> 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.

It's much easier, if a bit slower, to just run

  git branch -r --contains $commit

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2013-02-19 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19  9:38 Feature idea : notes to track status of a commit, which remotes it is shared to Mildred Ki'Lya
2013-02-19 10:13 ` Thomas Rast [this message]
2013-02-19 10:34   ` W. Trevor King
2013-02-19 18:55   ` Junio C Hamano
2013-02-19 10:30 ` W. Trevor King

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=87bobgtxvk.fsf@pctrast.inf.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=mildred-ml@mildred.fr \
    /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).