git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Joshua Shrader <jshrader83@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Git Notes on Branches
Date: Thu, 22 Jul 2010 16:05:54 -0500	[thread overview]
Message-ID: <20100722210554.GA17461@burratino> (raw)
In-Reply-To: <AANLkTinnDBUzoDj-C289l4Kui2qSiKmF-027MzijyCFY@mail.gmail.com>

Hi Joshua,

Joshua Shrader wrote:

> I'm wondering if there is a way to (or a reason that would prevent one
> from implementing a feature that allows one to) associate a note with
> a branch, rather than a specific object.

Except for the word “note”, I think your suggestion does not have
anything to do with git notes at all. :)

Special support in gitweb, ‘git branch’, and so on for a branch with
files named after branches and giving descriptions would seem sane
to me.

Here’s something similar for inspiration:

  http://thread.gmane.org/gmane.comp.version-control.git/33528/focus=33563

Good luck,
Jonathan

      reply	other threads:[~2010-07-22 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 20:22 Git Notes on Branches Joshua Shrader
2010-07-22 21:05 ` Jonathan Nieder [this message]

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=20100722210554.GA17461@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jshrader83@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.
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).