From: Joey Hess <joey@kitenet.net>
To: git@vger.kernel.org
Subject: Re: git notes: notes
Date: Wed, 20 Jan 2010 13:24:38 -0500 [thread overview]
Message-ID: <20100120182438.GB31507@gnu.kitenet.net> (raw)
In-Reply-To: <201001201148.11701.johan@herland.net>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
Johan Herland wrote:
> As Thomas already stated, git log is porcelain, and its output format is not
> set in stone. If you need a stable, script-friendly format, you should
> probably use the --format option, or use plumbing instead (such as e.g. git
> rev-list, which also has a --format option).
But git log --format=raw --raw output was changed by notes.
> > Might be worth documenting in release notes, maybe too late now though.
> > But really, it's all good, notes are a great feature.
> >
> > PS, Has anyone thought about using notes to warn bisect away from
> > commits that are known to be unbuildable or otherwise cause bisection
> > trouble?
>
> No, I haven't thought of that specific use case. Great idea! :)
Only problem I see with doing it is it might be too easy to overwrite
such a note with git notes edit -m
Did you consider having -m append a line to an existing note?
--
see shy jo
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2010-01-20 18:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 5:03 git notes: notes Joey Hess
2010-01-20 9:48 ` Thomas Rast
2010-01-20 18:14 ` Joey Hess
2010-01-20 10:48 ` Johan Herland
2010-01-20 18:24 ` Joey Hess [this message]
2010-01-20 19:30 ` Junio C Hamano
2010-01-20 19:56 ` Joey Hess
2010-01-20 20:10 ` Junio C Hamano
2010-01-20 20:36 ` Joey Hess
2010-01-20 20:54 ` Jeff King
2010-01-20 20:59 ` Junio C Hamano
2010-01-20 21:31 ` Jeff King
2010-01-20 21:41 ` Jeff King
2010-01-20 22:07 ` Junio C Hamano
2010-01-20 22:21 ` Jeff King
2010-01-20 21:02 ` Michael J Gruber
2010-01-20 21:08 ` Junio C Hamano
2010-01-20 21:36 ` Jeff King
2010-01-20 21:59 ` Junio C Hamano
2010-01-20 22:25 ` Jeff King
2010-01-20 22:33 ` Junio C Hamano
2010-01-20 22:58 ` Johannes Schindelin
2010-01-20 23:06 ` Jeff King
2010-01-20 23:14 ` Junio C Hamano
2010-01-21 2:54 ` Johan Herland
2010-01-21 3:03 ` Junio C Hamano
2010-01-21 3:37 ` Junio C Hamano
2010-01-21 8:45 ` Michael J Gruber
2010-01-24 14:20 ` Matthieu Moy
2010-01-24 14:27 ` Sverre Rabbelier
2010-01-21 2:05 ` Johan Herland
2010-01-21 3:59 ` Johannes Schindelin
2010-01-21 4:05 ` Joey Hess
2010-01-27 11:55 ` Johan Herland
2010-01-25 18:08 ` John Koleszar
2010-01-27 20:01 ` Christian Couder
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=20100120182438.GB31507@gnu.kitenet.net \
--to=joey@kitenet.net \
--cc=git@vger.kernel.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.
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).