From: "J. Bruce Fields" <bfields@fieldses.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Yann Dirson <ydirson@altern.org>,
Catalin Marinas <catalin.marinas@gmail.com>,
git <git@vger.kernel.org>, Charles Lever <cel@citi.umich.edu>
Subject: Re: StGIT: "stg new" vs "stg new --force"
Date: Fri, 20 Jan 2006 13:22:55 -0500 [thread overview]
Message-ID: <20060120182255.GD32177@fieldses.org> (raw)
In-Reply-To: <1137738224.27911.26.camel@dv>
On Fri, Jan 20, 2006 at 01:23:44AM -0500, Pavel Roskin wrote:
> On Thu, 2006-01-19 at 22:38 +0100, Yann Dirson wrote:
> > That command could be "cat" to get the current "refresh" behaviour, or
> > an editor wrapper acting on stdin/out, or a wrapper to filterdiff, or
> > whatever clever filter one would want to use.
> >
> > Does it sound better ?
>
> Yes. The first step would be to fix "stg refresh --edit --showpatch" to
> actually respect edits made to the patch.
I tend to use stg refresh -es as a quick (well, not quite as quick as
I'd like) way to look at the current patch. Often I leave it up while
I'm working (editing the patched files). So if exiting from stg refresh
-es suddenly started overwriting my working files, I'd be very
unhappy....
--b.
next prev parent reply other threads:[~2006-01-20 18:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 9:24 StGIT: "stg new" vs "stg new --force" Pavel Roskin
2006-01-13 9:34 ` Karl Hasselström
2006-01-16 8:18 ` Catalin Marinas
2006-01-17 17:01 ` Pavel Roskin
2006-01-17 21:57 ` Yann Dirson
2006-01-17 23:16 ` Pavel Roskin
2006-01-18 19:37 ` Yann Dirson
2006-01-19 0:49 ` Pavel Roskin
2006-01-19 21:38 ` Yann Dirson
2006-01-20 6:23 ` Pavel Roskin
2006-01-20 18:22 ` J. Bruce Fields [this message]
2006-01-24 5:30 ` Pavel Roskin
2006-01-24 17:54 ` J. Bruce Fields
2006-01-24 18:17 ` Pavel Roskin
2006-01-24 21:23 ` Catalin Marinas
2006-01-21 18:24 ` Catalin Marinas
2006-01-22 5:05 ` Pavel Roskin
2006-01-21 18:20 ` Catalin Marinas
2006-01-21 18:31 ` Catalin Marinas
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=20060120182255.GD32177@fieldses.org \
--to=bfields@fieldses.org \
--cc=catalin.marinas@gmail.com \
--cc=cel@citi.umich.edu \
--cc=git@vger.kernel.org \
--cc=proski@gnu.org \
--cc=ydirson@altern.org \
/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).