GNU bug report logs - #8623
23.3.50; (woman "git-remote") crashes

Previous Next

Full log

Message #66 received at 8623-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: svenjoac <at> gmx.de, 8623-done <at> debbugs.gnu.org
Subject: Re: bug#8623: 23.3.50; (woman "git-remote") crashes
Date: Tue, 10 May 2011 11:13:21 +0300

> Date: Tue, 10 May 2011 00:56:24 -0700
> From: Paul Eggert <eggert <at> cs.ucla.edu>
> CC: svenjoac <at> gmx.de, 8623-done <at> debbugs.gnu.org
> 
> On 05/09/11 03:10, Eli Zaretskii wrote:
> > Paul, would it be possible for you to merge individual features or
> > bugfixes?
> 
> When I did this in the past, I was asked not to commit
> so many changes individually, but rather, to merge them
> in as a batch.

That's a strange request, but if that's what The Powers That Be want,
fine.

> > Or at least clearly mark in the commit logs where a fix for
> > a particular problem begins and where it ends?
> 
> I'll do that when I can, but when bugs are tricky (which this
> one was) I don't really know when the fix "ends".  I often
> later find glitches in what I at first thought was a complete
> bugfix or feature.  This is almost always before I merge
> in a batch of changes, but sometimes it's even after that.

Well, when you find that, could you perhaps add something like
"Completes such-and-such fix" to the log message?

> Thanks for backporting the fix, and sorry it was such a hassle.

It wasn't a terrible hassle, actually.  It's just that I mistakenly
decided that a single commit was needed, and then was faced with
compiler errors.  I originally thought that the errors were due to my
botched conflict resolution, and only after fixing a few of them I
looked back at the commit log and found that a couple more commits
were also needed in order to get a clean compile.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.