I found what the problem is. "git commit" discards all lines starting
with # in the log message (it uses that prefix to add comment lines
that show up in the editor when the editor is used to compose the log
message).
I think it is a bug in git-commit, which should not mess with the
message that way unless the editor was openned - I'll submit a patch
to git for this.
OTOH, we may not want to wait for a new git release to get git support
working again, and anyway tailor should probably not make use of
git-commit, which is a too high-level tool for such a job. I'll look
at that during the week-end, and will submit a proper patch for
tailor.
On Mon, May 29, 2006 at 04:07:22PM +0200, Yann DIRSON wrote:
> As mentionned in the previous mail, this is a private repo.
> Using "stderr=PIPE" and printing "err.read()" says the following. I new I
> had seen a "no commit message?" at some point :)
> Any idea why would that one commit fail, and not all the previous ones ?
>
> 16:00:13 [I] Updating "trunk" in "/homelocal/ydirson/test/trunk-in"
> 16:00:13 [I] Applying pending upstream changesets
> 16:00:13 [I] Changeset "2006-05-09 09:40:55 by csousbie"
> 16:00:13 [I] Log message: #65 cahier d'int?gration : ajout de "synchronize"
> devant la methode erHandleMessageInfoCommande
> 16:00:13 [I] /homelocal/ydirson/test/trunk-in $ git commit -a -F -
> 16:00:14 [W] [Status 1]
> 16:00:14 [C] Couldn't replay changeset
> 16:00:14 [C] Upstream change application failed
> Failure applying upstream changes: /homelocal/ydirson/test/trunk-in $ git
> commit -a -F - returned status 1 saying * no commit message? aborting
> commit.
--
Yann Dirson <[EMAIL PROTECTED]> |
Debian-related: <[EMAIL PROTECTED]> | Support Debian GNU/Linux:
| Freedom, Power, Stability, Gratis
http://ydirson.free.fr/ | Check <http://www.debian.org/>
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
