From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [BUG] StGit removed git branch of the same name as StGit branch
Date: Mon, 20 Nov 2006 17:48:00 -0500 [thread overview]
Message-ID: <20061120224800.GF12285@fieldses.org> (raw)
In-Reply-To: <ejtal6$p8s$1@sea.gmane.org>
On Mon, Nov 20, 2006 at 11:37:54PM +0100, Jakub Narebski wrote:
> J. Bruce Fields wrote:
> > You probably actually had to "stg branch --delete --force", didn't you?
>
> Nope. "stg branch --delete gitweb/web"
>
> > What you want is "stg commit".
>
> No. Whole stack was committed, I wanted only get rid of
> heads/base/gitweb/web (of StGit managed branch indicator).
Oh, right, got it.
> > The idea I guess was to make it possible to use stgit (and only stgit)
> > for everything, and never type a git command. It might have been better
> > to make stgit only manage patch series, and admit that people should use
> > git for the rest. Then it might work more like you expect.
>
> Yes, I expected to use StGit as a kind of preprocessing (branch preparation)
> for git.
The multiple-porcelains idea seems like a mistake to me--it'd be fine if
you're just adding new features on the side, but who wants to learn
entirely different sets of commands, with subtly different syntax,
semantics, and feature sets, for doing the same thing?
next prev parent reply other threads:[~2006-11-20 22:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 21:01 [BUG] StGit removed git branch of the same name as StGit branch Jakub Narebski
2006-11-20 21:08 ` Junio C Hamano
2006-11-20 22:28 ` J. Bruce Fields
2006-11-20 22:37 ` Jakub Narebski
2006-11-20 22:48 ` J. Bruce Fields [this message]
2006-11-20 22:57 ` Jakub Narebski
2006-11-20 23:53 ` Carl Worth
2006-11-21 10:06 ` Catalin Marinas
2006-11-21 10:56 ` Karl Hasselström
2006-11-21 9:26 ` Catalin Marinas
2006-11-21 10:07 ` Jakub Narebski
2006-11-21 10:19 ` Catalin Marinas
2006-11-21 10:48 ` Jakub Narebski
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=20061120224800.GF12285@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).