git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [StGit PATCH] Check for local changes with "goto"
Date: Thu, 15 Jan 2009 22:24:53 +0000	[thread overview]
Message-ID: <b0943d9e0901151424m49f6869cq1255cf841703dc9d@mail.gmail.com> (raw)
In-Reply-To: <20090115083700.GB24890@diana.vm.bytemark.co.uk>

2009/1/15 Karl Hasselström <kha@treskal.com>:
> I'm not opposed to the change as such (even if I personally think it's
> very convenient to allow operations like goto if the local changes
> don't touch the same files), but ...

That would work if "refresh" only commits files previously added to
the patch (the same way as quilt). I found myself many times moving to
another patch and refreshing more than I wanted to add to that patch
because I forgot to run "status" before "goto".

Maybe we can make this configurable to accommodate both variants
(would be even easier if I move the check to transaction.py).

> On 2009-01-14 22:59:45 +0000, Catalin Marinas wrote:
>
>>  stgit/commands/common.py  |    7 +++++++
>>  stgit/commands/goto.py    |    8 +++++++-
>
> ... are you sure it wouldn't be better to build the check into
> transaction.py, so that all new-infrastructure command would share it?

OK, I'll do this and repost.

-- 
Catalin

  reply	other threads:[~2009-01-15 22:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 22:59 [StGit PATCH] Check for local changes with "goto" Catalin Marinas
2009-01-15  8:37 ` Karl Hasselström
2009-01-15 22:24   ` Catalin Marinas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-28 23:13 Catalin Marinas
2009-01-29  3:45 ` Karl Hasselström
2009-01-30 14:01   ` Catalin Marinas
2009-01-30 15:26     ` Karl Hasselström
2009-01-30 17:36       ` Catalin Marinas
2009-02-06 14:46         ` Catalin Marinas
2009-02-06 15:31           ` Karl Hasselström
2009-02-06 18:39             ` Catalin Marinas
2009-02-10 14:11 Catalin Marinas
2009-02-11  9:05 ` 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=b0943d9e0901151424m49f6869cq1255cf841703dc9d@mail.gmail.com \
    --to=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).