git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Reuse previous annotation when overwriting a tag

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 3, 2007, 12:23 UTC
Message-ID
<Pine.LNX.4.64.0711031219530.4362@racer.site>
In-Reply-To
<20071103121002.GA4295@glandium.org>
Hi,
On Sat, 3 Nov 2007, Mike Hommey wrote:
Show 16 quoted lines
> 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.
Show 9 quoted lines
> (...)
> > 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.

Show 6 quoted lines
> (...)
> > 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

Previous: Mike HommeyNext: Mike Hommey
Message 4 of 16 in “Reuse previous annotation when overwriting a tag”
  1. Reuse previous annotation when overwriting a tagMike Hommey, Nov 3, 2007
  2. Johannes SchindelinNov 3, 2007
  3. Mike HommeyNov 3, 2007
  4. Johannes SchindelinNov 3, 2007
  5. 1/2 Reuse previous annotation when overwriting a tagMike Hommey, Nov 3, 2007
  6. 2/2 Small code readability improvement in show_reference() in builtin-tag.cMike Hommey, Nov 3, 2007
  7. Mike HommeyNov 7, 2007
  8. Junio C HamanoNov 3, 2007
  9. Mike HommeyNov 3, 2007
  10. 1/2 Reuse previous annotation when overwriting a tagMike Hommey, Nov 4, 2007
  11. 2/2 Add tests for git tagMike Hommey, Nov 4, 2007
  12. Mike HommeyNov 3, 2007
  13. Johannes SchindelinNov 3, 2007
  14. Mike HommeyNov 3, 2007
  15. Johannes SchindelinNov 3, 2007
  16. Mike HommeyNov 3, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.