From: Alexandre Julliard <julliard@winehq.org>
To: "David Kågedal" <davidk@lysator.liu.se>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git.el: Only show completions from refs/heads
Date: Tue, 03 Mar 2009 15:48:51 +0100 [thread overview]
Message-ID: <87tz6aslv0.fsf@wine.dyndns.org> (raw)
In-Reply-To: <87zlg4qsfk.fsf@krank.kagedal.org> ("David Kågedal"'s message of "Mon, 02 Mar 2009 08:45:19 +0100")
David Kågedal <davidk@lysator.liu.se> writes:
> Yes, but the typical uses differ a lot. The (overwhelmingly) typical
> use of checkout is to switch to another branch. The typical use of
> cherry-pick is to pick any commit and not treat branch heads
> specially.
>
> So when switching branches, I obviously want a simple way to select
> which branch to switch to. When cherry-picking, I would need some
> simple way of picking any single commit, but that's hard so making it
> easy to pick any named commit is probably the reasonable solution.
It sounds like what you want is to customize it independently for each
operation. That would be better than having two completion functions,
where it's not clear how they differ and why only one can be
customized.
--
Alexandre Julliard
julliard@winehq.org
prev parent reply other threads:[~2009-03-03 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 8:32 [PATCH] git.el: Only show completions from refs/heads, refs/remotes and refs/tags David Kågedal
2009-02-24 8:39 ` David Kågedal
2009-02-24 8:42 ` David Kågedal
2009-02-24 14:50 ` Alexandre Julliard
2009-02-24 15:40 ` David Kågedal
2009-02-24 15:47 ` Alexandre Julliard
2009-02-24 15:57 ` David Kågedal
2009-02-24 16:06 ` Alexandre Julliard
2009-02-24 20:39 ` [PATCH] git.el: Only show completions from refs/heads David Kågedal
2009-03-01 16:56 ` Alexandre Julliard
2009-03-02 7:45 ` David Kågedal
2009-03-03 14:48 ` Alexandre Julliard [this message]
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=87tz6aslv0.fsf@wine.dyndns.org \
--to=julliard@winehq.org \
--cc=davidk@lysator.liu.se \
--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.