From: Petr Baudis <pasky@suse.cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Marco Costalba <mcostalba@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC] just an (stupid) idea when creating a new branch
Date: Mon, 10 Jul 2006 00:01:16 +0200 [thread overview]
Message-ID: <20060709220116.GT29115@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.63.0607091632070.29667@wbgn013.biozentrum.uni-wuerzburg.de>
Hi,
Dear diary, on Sun, Jul 09, 2006 at 04:33:53PM CEST, I got a letter
where Johannes Schindelin <Johannes.Schindelin@gmx.de> said that...
> On Sun, 9 Jul 2006, Marco Costalba wrote:
>
> > It is possible to add a message (and more) to a tag creating a tag
> > object. FWIK this is not allowed for the other refs.
> >
> > Why there is this (artifical?) difference between tags and the other
> > kind of refs?
>
> The tag message is nothing else than a commit message.
huh?
The tag message is a message in the "freeform" part of the tag object,
but disregarding the format similiraties, it has really nothing to do
with a commit message. (Also, commit messages don't tend to be commonly
PGP signed. ;-)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam
next prev parent reply other threads:[~2006-07-09 22:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 15:55 [RFC] just an (stupid) idea when creating a new branch moreau francis
2006-07-08 21:41 ` Jakub Narebski
2006-07-08 22:15 ` Johannes Schindelin
2006-07-09 17:04 ` Jakub Narebski
2006-07-09 19:09 ` Johannes Schindelin
2006-07-09 6:54 ` Marco Costalba
2006-07-09 14:33 ` Johannes Schindelin
2006-07-09 22:01 ` Petr Baudis [this message]
2006-07-09 22:12 ` Johannes Schindelin
2006-07-09 3:27 ` Pavel Roskin
2006-07-09 9:48 ` Re : " moreau francis
2006-07-09 10:16 ` Junio C Hamano
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=20060709220116.GT29115@pasky.or.cz \
--to=pasky@suse.cz \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mcostalba@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).