From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [BUG] StGit removed git branch of the same name as StGit branch
Date: Mon, 20 Nov 2006 23:37:54 +0100 [thread overview]
Message-ID: <ejtal6$p8s$1@sea.gmane.org> (raw)
In-Reply-To: 20061120222812.GE12285@fieldses.org
J. Bruce Fields wrote:
> On Mon, Nov 20, 2006 at 10:01:44PM +0100, Jakub Narebski wrote:
>
>> I have used StGit (wonderfull tool) to manage patches on git branch
>> gitweb/web. Unfortunately, I have named stg branch the same as git
>> branch. When removing stg branch (I wanted to remove
>> heads/base/gitweb/web) using "stg branch --delete gitweb/web" it
>> deleted also git branch when I wanted to remove only the StGit managed
>> indicator.
>
> 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).
>> Perhaps that is correct behavior... but certainly unexpected.
>
> I think "stg branch --delete" is pretty clearly named and documented....
I thought it delete only stg branch, refs/base/gitwbe/web, and not
refs/heads/gitweb/web.
> 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.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-11-20 22:37 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 [this message]
2006-11-20 22:48 ` J. Bruce Fields
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='ejtal6$p8s$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.