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

Re: [PATCH] parsecvs: produce tagger fields acceptable to newer git versions

From
LBLennert Buytenhek <buytenh@wantstofly.org>
Date
Jan 19, 2009, 13:39 UTC
Message-ID
<20090119133907.GF4390@xi.wantstofly.org>
In-Reply-To
<87ab9nbh49.fsf@meyering.net>
On Mon, Jan 19, 2009 at 01:44:06PM +0100, Jim Meyering wrote:
Show 24 quoted lines
> > Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
> >
> > diff --git a/git.c b/git.c
> > index da320d1..8f94d1b 100644
> > --- a/git.c
> > +++ b/git.c
> > @@ -371,11 +371,13 @@ git_mktag (rev_commit *commit, char *name)
> >  		"object %s\n"
> >  		"type commit\n"
> >  		"tag %s\n"
> > -		"tagger %s\n"
> > +		"tagger %s <%s> %lu +0000\n"
> >  		"\n",
> >  		commit->sha1,
> >  		name,
> > -		author ? author->full : commit->author);
> > +		author ? author->full : commit->author,
> > +		author ? author->email : commit->author,
> > +		commit->date);
> >      if (rv < 1) {
> >  	fprintf (stderr, "%s: %s\n", filename, strerror (errno));
> >  	fclose (f);
> 
> Hi Lennert,
Hey Jim,
Show 7 quoted lines
> I posted the same patch a while back.
> 
>     http://markmail.org/message/cebh7suc7ejpayos
> 
> However, I never heard back.
> You'll also need the patch below, if you're building
> against a newer version of git.
Can you make your parsecvs repository available somewhere?

thanks, Lennert

Previous: Jim Meyering
Message 3 of 3 in “parsecvs: produce tagger fields acceptable to newer git versions”
  1. parsecvs: produce tagger fields acceptable to newer git versionsLennert Buytenhek, Jan 19, 2009
  2. Jim MeyeringJan 19, 2009
  3. Lennert BuytenhekJan 19, 2009

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.