From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Mike Hommey <mh@glandium.org>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Reuse previous annotation when overwriting a tag
Date: Sat, 3 Nov 2007 12:23:55 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711031219530.4362@racer.site> (raw)
In-Reply-To: <20071103121002.GA4295@glandium.org>
Hi,
On Sat, 3 Nov 2007, Mike Hommey wrote:
> On Sat, Nov 03, 2007 at 11:54:38AM +0000, Johannes Schindelin wrote:
> > > +{
> > > + int i;
> > > + unsigned long size;
> > > + enum object_type type;
> > > + char *buf, *sp, *eol;
> > > + size_t len;
> > > +
> > > + sp = buf = read_sha1_file(sha1, &type, &size);
> > > + if (!buf)
> > > + return;
> > > + if (!size || (type != OBJ_TAG)) {
> >
> > Please lose the extra parents.
>
> What do you mean ?
Typo. I meant the parens, and my fingers typed parents. D'oh.
> (...)
> > This can be done much easier with 'sp = strstr(buf, "\n\n");'. You can
> > even do that before the previous if(), to free() && return if there is no
> > body.
> (...)
> > This can be done much easier with 'eob = strstr(sp, "\n" PGP_SIGNATURE
> > "\n");'.
>
> I must say I just stole most of it in show_reference() in the same file.
I agree for the "\n\n"; this was my mistake (IOW it should be fixed both
in show_reference() as well as in your code).
But for the signature, show_reference() _has_ to go line by line, because
the user is allowed to specify a maximal line count. This does not apply
for your function.
> (...)
> > Why not teach write_annotations() (or write_tag_body() like I would prefer
> > it to be called) to grok a null_sha1? It's not like we care for
> > performance here, but rather for readability and ease of use.
>
> I would have if I had looked up for is_null_sha1() earlier ;)
Hehe. This is what I really like about git's mailing list: it is a place
where you learn something new every day.
Ciao,
Dscho
next prev parent reply other threads:[~2007-11-03 12:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 9:31 [PATCH] Reuse previous annotation when overwriting a tag Mike Hommey
2007-11-03 11:54 ` Johannes Schindelin
2007-11-03 12:10 ` Mike Hommey
2007-11-03 12:23 ` Johannes Schindelin [this message]
2007-11-03 13:08 ` [PATCH 1/2] " Mike Hommey
2007-11-03 13:08 ` [PATCH 2/2] Small code readability improvement in show_reference() in builtin-tag.c Mike Hommey
2007-11-07 21:51 ` Mike Hommey
2007-11-03 18:47 ` [PATCH 1/2] Reuse previous annotation when overwriting a tag Junio C Hamano
2007-11-03 19:55 ` Mike Hommey
2007-11-04 0:11 ` Mike Hommey
2007-11-04 0:11 ` [PATCH 2/2] Add tests for git tag Mike Hommey
2007-11-03 12:27 ` [PATCH] Reuse previous annotation when overwriting a tag Mike Hommey
2007-11-03 12:36 ` Johannes Schindelin
2007-11-03 13:10 ` Mike Hommey
2007-11-03 13:22 ` Johannes Schindelin
2007-11-03 13:59 ` Mike Hommey
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=Pine.LNX.4.64.0711031219530.4362@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mh@glandium.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).