From: David Bremner <david@tethera.net>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH] notmuch-dev: Forcibly delete branches.
Date: Fri, 13 Jan 2012 08:25:32 -0400 [thread overview]
Message-ID: <87wr8v23ib.fsf@zancas.localnet> (raw)
In-Reply-To: <1326450329-10108-1-git-send-email-dme@dme.org>
On Fri, 13 Jan 2012 10:25:29 +0000, David Edmondson <dme@dme.org> wrote:
> `magit-delete-branch' runs "git branch -d <branch>", which refuses to
> delete branches that are not fully merged. Given that we don't care
> and don't want to be stalled, use "git branch -D <branch>" directly.
> ---
Yes, that seems to fix it.
Two more questions/comments.
- Should n-d-s-review-patch update to current master? perhaps with
prefix?
- I think more escaping of branch names is needed. In particular, branch
names with {} in them get created ok, but then don't work very well in
magit. E.g. running log I get "Args out of range: "face}s", 5, 10"
with the branch name
review/patch-v2-emacs-logically-group-def{custom,face}s
d
next prev parent reply other threads:[~2012-01-13 12:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 14:01 [PATCH] emacs: Helpers for notmuch developers David Edmondson
2012-01-06 3:39 ` David Bremner
2012-01-06 8:27 ` David Edmondson
2012-01-06 10:03 ` [PATCH v2] " David Edmondson
2012-01-07 11:53 ` David Bremner
2012-01-09 8:23 ` David Edmondson
2012-01-09 10:38 ` David Bremner
2012-01-09 11:16 ` David Edmondson
2012-01-13 3:04 ` David Bremner
2012-01-13 10:25 ` [PATCH] notmuch-dev: Forcibly delete branches David Edmondson
2012-01-13 12:25 ` David Bremner [this message]
2012-01-13 13:28 ` [PATCH 1/2] notmuch-dev: Remove more characters from branch names David Edmondson
2012-01-13 13:28 ` [PATCH 2/2] notmuch-dev: Update the master branch when requested David Edmondson
2012-01-13 21:03 ` Xavier Maillard
2012-01-16 9:07 ` David Edmondson
2012-01-16 21:19 ` Xavier Maillard
2012-01-06 22:56 ` [PATCH] emacs: Helpers for notmuch developers Tomi Ollila
2012-01-09 8:27 ` David Edmondson
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wr8v23ib.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=dme@dme.org \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).