git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Support tags in uncommit - use git_id instead of rev_parse

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
Oct 3, 2007, 20:35 UTC
Message-ID
<b0943d9e0710031335o1c7f3a10i6f2055b76376bfd4@mail.gmail.com>
In-Reply-To
<1191362591.26879.3.camel@dv>
On 02/10/2007, Pavel Roskin <proski@gnu.org> wrote:
Show 12 quoted lines
> On Mon, 2007-10-01 at 23:00 +0100, Catalin Marinas wrote:
> > To allow tags, maybe just pass something like
> > "git.rev_parse(options.to + '^{commit}')" or just modify git.rev_parse
> > to do it (and git_id to avoid it).
>
> I prefer to work with software that understands what I mean and tells me
> that I cannot do it.  It makes it easier to understand what is possible
> and how the command is working.
>
> Recognizing patch names in some commands but not others would be
> annoying and inconsistent.  Dumbing downs interactive software on
> purpose is probably not worth the trouble.

Without this patch, the 'stg uncommit -t patch' fails with 'Unknown revision: patch'. With the patch applied, it still fails but with 'Commit ... does not have exactly one parent'. I don't say that the first one is good but I don't think the latter is clearer. The 'stg uncommit --help' states that the '--to' option takes a commit argument but if one passes a patch name the error message gets pretty confusing.

-- 
Catalin
Previous: Pavel RoskinNext: Pavel Roskin
Message 5 of 7 in “Support tags in uncommit - use git_id instead of rev_parse”
  1. Support tags in uncommit - use git_id instead of rev_parsePavel Roskin, Sep 30, 2007
  2. Karl HasselströmOct 1, 2007
  3. Catalin MarinasOct 1, 2007
  4. Pavel RoskinOct 2, 2007
  5. Catalin MarinasOct 3, 2007
  6. Pavel RoskinOct 3, 2007
  7. Catalin MarinasOct 7, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.