From: Catalin Marinas <catalin.marinas@arm.com>
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: Tue, 21 Nov 2006 10:19:00 +0000 [thread overview]
Message-ID: <tnx1wnxxfu3.fsf@arm.com> (raw)
In-Reply-To: <ejuj2a$2ot$1@sea.gmane.org> (Jakub Narebski's message of "Tue, 21 Nov 2006 11:07:31 +0100")
Jakub Narebski <jnareb@gmail.com> wrote:
> Catalin Marinas wrote:
>> I've never thought anyone would see a different meaing for the
>> "branch" command. What you wanted to do was the reverse of the "init"
>> command. Maybe something like "uninit" or a "--uninit" option to
>> "branch".
>
> Yes, that is what I wanted. "stg branch --unmanage" or something
> like that.
I'll put it on my to-do list.
> By the way, why "stg branch --delete" doesn't remove reflog? Not that I'm
> complaining, because it sure saved some work when resurrecting branch, and
> I didn't loose reflog info.
Reflogs came into GIT after the StGIT branch command and never looked
at them in detail. And maybe it should not touch the reflog info,
especially for situations like this, unless GIT has a mechanism for a
trash bin (StGIT has one for patches - .git/patches/<branch>/trash/ -
but undocumented)
--
next prev parent reply other threads:[~2006-11-21 10:19 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
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 [this message]
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=tnx1wnxxfu3.fsf@arm.com \
--to=catalin.marinas@arm.com \
--cc=catalin.marinas@gmail.com \
--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.