From: Junio C Hamano <junkio@cox.net>
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 13:08:32 -0800 [thread overview]
Message-ID: <7vbqn125db.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200611202201.45521.jnareb@gmail.com> (Jakub Narebski's message of "Mon, 20 Nov 2006 22:01:44 +0100")
Jakub Narebski <jnareb@gmail.com> writes:
> 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. Fortunately I was able to recover the branch from reflog, as
> StGit didn't delete reflog with deletion of git branch.
>
> Perhaps that is correct behavior... but certainly unexpected.
I am also a novice who recently started appreciating the
convenience of StGIT. I _think_ the usage StGIT expect us to
follow is to run "stg clean" to make the series empty, and not
worry about leftover refs/bases/ at all, but I may well be
mistaken.
next prev parent reply other threads:[~2006-11-20 21:10 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 [this message]
2006-11-20 22:28 ` J. Bruce Fields
2006-11-20 22:37 ` Jakub Narebski
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=7vbqn125db.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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 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.