Git development
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] prompt: squelch error output from cat
Date: Fri, 14 Jun 2013 15:58:16 +0200	[thread overview]
Message-ID: <20130614135816.GL2091@goldbirke> (raw)
In-Reply-To: <CALkWK0kwVahUF_kwk4jRr7Qr5_H-FY_aXWLkQcaZV-YrV_mgjw@mail.gmail.com>

On Thu, Jun 13, 2013 at 08:15:59PM +0530, Ramkumar Ramachandra wrote:
> SZEDER Gábor wrote:
> > 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

  reply	other threads:[~2013-06-14 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 13:46 [PATCH] prompt: squelch error output from cat Ramkumar Ramachandra
2013-06-13 14:39 ` SZEDER Gábor
2013-06-13 14:45   ` Ramkumar Ramachandra
2013-06-14 13:58     ` SZEDER Gábor [this message]
2013-06-15 15:33 ` SZEDER Gábor

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=20130614135816.GL2091@goldbirke \
    --to=szeder@ira.uka.de \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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