From: Shawn Pearce <spearce@spearce.org>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>,
Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: update-ref logs: problem with committer info?
Date: Fri, 4 Aug 2006 22:56:00 -0400 [thread overview]
Message-ID: <20060805025600.GA18223@spearce.org> (raw)
In-Reply-To: <000501c6b809$2b18cd60$c47eedc1@ramsay1.demon.co.uk>
Ramsay Jones <ramsay@ramsay1.demon.co.uk> wrote:
> diff --git a/builtin-update-ref.c b/builtin-update-ref.c
> index 00333c7..83094ab 100644
> --- a/builtin-update-ref.c
> +++ b/builtin-update-ref.c
> @@ -12,6 +12,7 @@ int cmd_update_ref(int argc, const char
> unsigned char sha1[20], oldsha1[20];
> int i;
>
> + setup_ident();
> setup_git_directory();
> git_config(git_default_config);
> diff --git a/refs.c b/refs.c
> index 713ca46..a4060d8 100644
> --- a/refs.c
> +++ b/refs.c
> @@ -379,7 +379,6 @@ static int log_ref_write(struct ref_lock
> lock->log_file, strerror(errno));
> }
>
> - setup_ident();
> comitter = git_committer_info(1);
> if (msg) {
> maxlen = strlen(comitter) + strlen(msg) + 2*40 + 5;
These two changes were already fixed by me in 0b0fe4a6 on July
10th. That change is in `next`, in `master` and in v1.4.2-rc3.
So I expect it to be available in a final release real-soon-now.
Maybe you should consider running a newer version of GIT?
> diff --git a/http-fetch.c b/http-fetch.c
> index 44eba5f..fe3a4fd 100644
> --- a/http-fetch.c
> +++ b/http-fetch.c
> @@ -1222,6 +1222,7 @@ int main(int argc, char **argv)
> int arg = 1;
> int rc = 0;
>
> + setup_ident();
> setup_git_directory();
> git_config(git_default_config);
>
> diff --git a/local-fetch.c b/local-fetch.c
> index ffa4887..d059a51 100644
> --- a/local-fetch.c
> +++ b/local-fetch.c
> @@ -207,6 +207,7 @@ int main(int argc, char **argv)
> char *commit_id;
> int arg = 1;
>
> + setup_ident();
> setup_git_directory();
> git_config(git_default_config);
>
> diff --git a/ssh-fetch.c b/ssh-fetch.c
> index 1e59cd2..a42d17e 100644
> --- a/ssh-fetch.c
> +++ b/ssh-fetch.c
> @@ -131,6 +131,7 @@ int main(int argc, char **argv)
> prog = getenv("GIT_SSH_PUSH");
> if (!prog) prog = "git-ssh-upload";
>
> + setup_ident();
> setup_git_directory();
> git_config(git_default_config);
>
These changes aren't in `next` right now, but should be. Junio,
can you apply them?
--
Shawn.
next prev parent reply other threads:[~2006-08-05 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 21:01 update-ref logs: problem with committer info? Ramsay Jones
2006-08-05 2:56 ` Shawn Pearce [this message]
2006-08-05 20:23 ` Ramsay Jones
2006-08-05 20:33 ` Shawn Pearce
2006-08-05 23:55 ` Robin Rosenberg
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=20060805025600.GA18223@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=ramsay@ramsay1.demon.co.uk \
/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).