Re: StGIT: "stg new" vs "stg new --force"

From: J. Bruce Fields <bfields@fieldses.org>
Date: Jan 24, 2006, 17:54 UTC
Message-ID: <20060124175443.GA29670@fieldses.org>
In-Reply-To: <1138080623.15105.51.camel@dv>

On Tue, Jan 24, 2006 at 12:30:23AM -0500, Pavel Roskin wrote:

Show 9 quoted lines

> On Fri, 2006-01-20 at 13:22 -0500, J. Bruce Fields wrote:
> > 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....
> 
> If I understand correctly, "stg refresh" only modifies the repository,
> not the files in the local directory.

Well, yeah, but the reason that makes sense is that it's modifying the repository to bring it up to date with the working directory.

> This shouldn't change.

So after you hand-edit the diff and exit "stg refresh -es", the top of the current patch will no longer agree with the state of the working directory. What are you going to do on the next refresh? Or on the next push or pop? This seems a little confusing.

--b.