RE: update-ref logs: problem with committer info?
- From
Ramsay Jones <ramsay@ramsay1.demon.co.uk>
- Date
- Aug 5, 2006, 20:23 UTC
- Message-ID
- <001a01c6b8cd$0a7b5860$c47eedc1@ramsay1.demon.co.uk>
- In-Reply-To
- <20060805025600.GA18223@spearce.org>
On Sat 2006-08-05 at 3:56, spearce@spearce.org wrote:
Show 30 quoted lines
> 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?
>Yes, I am quite a long way behind, at version 1.4.1, which is light-years in git-time! Unfortunately, since I can't pull from the git repo (I don't have internet access from Linux), I won't be able to update until the v1.4.2 tar-ball is posted. Yep, not exactly ideal.
OK, for now I will refrain from contributing, at least until v1.4.2 is out.
Sorry for the noise.
Ramsay