Git development
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Jim Meyering <jim@meyering.net>
Cc: keithp@keithp.com, git@vger.kernel.org, jay@gnu.org, kedars@marvell.com
Subject: Re: [PATCH] parsecvs: produce tagger fields acceptable to newer git versions
Date: Mon, 19 Jan 2009 14:39:07 +0100	[thread overview]
Message-ID: <20090119133907.GF4390@xi.wantstofly.org> (raw)
In-Reply-To: <87ab9nbh49.fsf@meyering.net>

On Mon, Jan 19, 2009 at 01:44:06PM +0100, Jim Meyering wrote:

> > 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,


> 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

      reply	other threads:[~2009-01-19 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19 12:02 [PATCH] parsecvs: produce tagger fields acceptable to newer git versions Lennert Buytenhek
2009-01-19 12:44 ` Jim Meyering
2009-01-19 13:39   ` Lennert Buytenhek [this message]

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=20090119133907.GF4390@xi.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=git@vger.kernel.org \
    --cc=jay@gnu.org \
    --cc=jim@meyering.net \
    --cc=kedars@marvell.com \
    --cc=keithp@keithp.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