git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jonas Kittner" <jonas.kittner@ruhr-uni-bochum.de>
To: <git@vger.kernel.org>
Subject: `BUG: sequencer.c:921: GIT_AUTHOR_DATE missing from author script` when trying to reword in interactive rebase
Date: Tue, 2 Nov 2021 00:17:29 +0100	[thread overview]
Message-ID: <000201d7cf76$a4861460$ed923d20$@ruhr-uni-bochum.de> (raw)

Hello,
I encountered the following bug and filled out the template provided with
`git bugreport` below.
Kind Regards,
Jonas Kittner

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)

In the interactive prompt I changed `pick` to `reword`, saved and closed the
prompt.
Commands to repoduce see below

```
root@135b2edea980:/# git init bug
Initialized empty Git repository in /bug/.git/
root@135b2edea980:/# cd bug/
root@135b2edea980:/bug# touch foo
root@135b2edea980:/bug# git add .
root@135b2edea980:/bug# git commit -m "foo"
[master (root-commit) 8fef261] foo
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 foo
root@135b2edea980:/bug# touch bar
root@135b2edea980:/bug# git add .
root@135b2edea980:/bug# git commit -m "bar"
[master 79a46e6] bar
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 bar
root@135b2edea980:/bug# git log --oneline
79a46e6 (HEAD -> master) bar
8fef261 foo
root@135b2edea980:/bug# git rebase --interactive
--committer-date-is-author-date 8fef261
BUG: sequencer.c:921: GIT_AUTHOR_DATE missing from author script
Aborted (core dumped)
root@135b2edea980:/bug# git --version
git version 2.33.1
```

What did you expect to happen? (Expected behavior)
I expected to be able to reword the commit message like without passing the
`--committer-date-is-author-date` argument.


What happened instead? (Actual behavior)
segfault: `BUG: sequencer.c:921: GIT_AUTHOR_DATE missing from author script`

What's different between what you expected and what actually happened?
wouldn't expect a segfault, but the option to be able to edit the commit
message

Anything else you want to add:
This was inside an ubuntu focal docker container, git was installed via the
ppa ` ppa:git-core/ppa`

https://github.com/git/git/commit/7573cec52c0274ceb166c425be4288f6b3103d6f#d
iff-0e574dc9087fc7831bbc1403545a8561f08869576c1ccc4146aa276146ff9777R888-R88
9
this seems to be not the case and needs to be handled differently I guess?


Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.33.1
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 20:41:07
UTC 2021 x86_64
compiler info: gnuc: 9.3
libc info: glibc: 2.31
$SHELL (typically, interactive shell): <unset>


[Enabled Hooks]



             reply	other threads:[~2021-11-01 23:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 23:17 Jonas Kittner [this message]
2021-11-02  1:27 ` `BUG: sequencer.c:921: GIT_AUTHOR_DATE missing from author script` when trying to reword in interactive rebase Jeff King
2021-11-02 12:20   ` Phillip Wood

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='000201d7cf76$a4861460$ed923d20$@ruhr-uni-bochum.de' \
    --to=jonas.kittner@ruhr-uni-bochum.de \
    --cc=git@vger.kernel.org \
    /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).