The files $g/rebase-{merge,apply}/{head-name,msgnum,end} are not
guaranteed to exist. When attempting to cat them, squelch the error
output to get rid of messages like these:
cat: .git/rebase-merge/msgnum: No such file or directory
cat: .git/rebase-merge/end: No such file or directory
Signed-off-by: Ramkumar Ramachandra <redacted>
---
contrib/completion/git-prompt.sh | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
From: SZEDER Gábor <hidden> Date: 2016-06-15 22:57:44
Hi,
On Thu, Jun 13, 2013 at 07:16:49PM +0530, Ramkumar Ramachandra wrote:
The files $g/rebase-{merge,apply}/{head-name,msgnum,end} are not
guaranteed to exist. When attempting to cat them, squelch the error
output to get rid of messages like these:
cat: .git/rebase-merge/msgnum: No such file or directory
cat: .git/rebase-merge/end: No such file or directory
Signed-off-by: Ramkumar Ramachandra <redacted>
Makes sense.
Just curious: when do those files don't exist? When using an older
version of git with a newer prompt, obviously, but are there other
cases?
Thanks,
Gábor
Just curious: when do those files don't exist? When using an older
version of git with a newer prompt, obviously, but are there other
cases?
# On terminal one
$ git rebase --interactive master
# Ignore editor, and open terminal two
cat: .git/rebase-merge/msgnum: No such file or directory
cat: .git/rebase-merge/end: No such file or directory
$
From: SZEDER Gábor <hidden> Date: 2016-06-15 22:57:45
On Thu, Jun 13, 2013 at 08:15:59PM +0530, Ramkumar Ramachandra wrote:
SZEDER Gábor wrote:
quoted
Just curious: when do those files don't exist? When using an older
version of git with a newer prompt, obviously, but are there other
cases?
# On terminal one
$ git rebase --interactive master
# Ignore editor, and open terminal two
cat: .git/rebase-merge/msgnum: No such file or directory
cat: .git/rebase-merge/end: No such file or directory
$
Interesting, I wouldn't have thought of that.
I was wondering whether there are cases and code paths in git rebase,
where it knows what to write into those files but it does not write
them, which might be worth fixing additionally. In case of this
halfway-started rebase I don't see any point in displaying 0/42, so I
don't think any additional fix would be necessary.
Thanks,
Gábor
From: SZEDER Gábor <hidden> Date: 2016-06-15 22:57:45
Hi Junio,
I see you picked up this patch in branch
'rr/prompt-autostash-breakage-fix'. This patch has actually nothing
to do with autostash, it is a fix for b71dc3e1 (bash-prompt.sh: show
where rebase is at when stopped, 2013-04-25).
Gábor
On Thu, Jun 13, 2013 at 07:16:49PM +0530, Ramkumar Ramachandra wrote:
quoted hunk
The files $g/rebase-{merge,apply}/{head-name,msgnum,end} are not
guaranteed to exist. When attempting to cat them, squelch the error
output to get rid of messages like these:
cat: .git/rebase-merge/msgnum: No such file or directory
cat: .git/rebase-merge/end: No such file or directory
Signed-off-by: Ramkumar Ramachandra <redacted>
---
contrib/completion/git-prompt.sh | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)