From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Paul Donohue" <stgit-bug@topquark.net>
Cc: git@vger.kernel.org
Subject: Re: Minor bug in 'stg edit' ?
Date: Thu, 28 Feb 2008 21:43:53 +0000 [thread overview]
Message-ID: <b0943d9e0802281343l7c3190a1va564a87afce1ea06@mail.gmail.com> (raw)
In-Reply-To: <20080227224756.GK2222@TopQuark.net>
On 27/02/2008, Paul Donohue <stgit-bug@topquark.net> wrote:
> I'm running StGIT 0.14.1
>
> After running 'stg edit', the file '.stgit-edit.txt' is always left behind.
>
> Is this supposed to happen? I would have assumed the file would be automatically removed after the changes were committed.
I wouldn't say it's a bug as I never thought it would cause any
problems if left. Anyway, we could remove it if the operation was
successful.
--
Catalin
next prev parent reply other threads:[~2008-02-28 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 22:47 Minor bug in 'stg edit' ? Paul Donohue
2008-02-28 9:41 ` Karl Hasselström
2008-02-28 21:43 ` Catalin Marinas [this message]
2008-02-28 21:54 ` Paul Donohue
2008-02-29 8:00 ` Karl Hasselström
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=b0943d9e0802281343l7c3190a1va564a87afce1ea06@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=stgit-bug@topquark.net \
/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).