From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org, "Catalin Marinas" <catalin.marinas@gmail.com>
Subject: Re: [StGit PATCH] Add some tests of refreshing removed files
Date: Mon, 4 Aug 2008 10:08:58 -0400 [thread overview]
Message-ID: <9e4733910808040708k69802d6w120fd88df7f92b7b@mail.gmail.com> (raw)
In-Reply-To: <9e4733910808040707u2ef8992eha629ebca9c41730b@mail.gmail.com>
On 8/4/08, Jon Smirl <jonsmirl@gmail.com> wrote:
> On 8/4/08, Karl Hasselström <kha@treskal.com> wrote:
> > Signed-off-by: Karl Hasselström <kha@treskal.com>
> >
> > ---
> >
> > These four tests all pass on Catalin's current master. Do they fail
> > for you, or did I miss something in your problem description?
>
>
> I just updated to current git and stg and retested. Tracking a remove
> is working now for me. Tools were about three months old before
> updating.
>
> Not sure what changed. But I definitely couldn't get stgit to do it
> and had to use git commands to generate the patch. I would remove the
> file, refresh and the patch was empty.
> stg status would show the file in D state. As soon as I touched
> something else and refreshed the rm would appear in the patch.
The file I was trying to rm was a hidden file, .mailmap
>
> Maybe there is more to the triggering sequence than a simple rm. I'll
> keep a watch out and see if I can figure out how I got into the state.
>
>
> --
> Jon Smirl
> jonsmirl@gmail.com
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-08-04 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 2:02 stgit and rm a file Jon Smirl
2008-08-04 13:41 ` [StGit PATCH] Add some tests of refreshing removed files Karl Hasselström
2008-08-04 14:07 ` Jon Smirl
2008-08-04 14:08 ` Jon Smirl [this message]
2008-08-04 14:43 ` 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=9e4733910808040708k69802d6w120fd88df7f92b7b@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.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;
as well as URLs for NNTP newsgroup(s).