From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Dan Williams" <dan.j.williams@intel.com>
Cc: git@vger.kernel.org
Subject: Re: [StGit] what happened to stg diff -r /{bottom|top}?
Date: Fri, 5 Dec 2008 22:26:44 +0000 [thread overview]
Message-ID: <b0943d9e0812051426m624c4889o314c1894114d1487@mail.gmail.com> (raw)
In-Reply-To: <49395CC9.2010107@intel.com>
2008/12/5 Dan Williams <dan.j.williams@intel.com>:
> I noticed that with the latest StGit:
> # stg diff -r /bottom
> stg diff: /bottom: Unknown patch or revision name
>
> Before I bisect to find where this disappeared, is there a different syntax
> I should be using?
In the development (master) branch, we changed the syntax to make it
cleaner. A patch (its top) can be identified as [<branch>:]<patch>. It
also supports standard Git suffixes like ^, ~{...} etc. To access the
bottom of a patch, just use [<branch>:]<patch>^.
The bottom of the top patch could be accessed as HEAD^ (I've been
thinking about only allowing the caret for this, without the HEAD but
I didn't have time to try it).
--
Catalin
prev parent reply other threads:[~2008-12-05 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 16:54 [StGit] what happened to stg diff -r /{bottom|top}? Dan Williams
2008-12-05 22:26 ` Catalin Marinas [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=b0943d9e0812051426m624c4889o314c1894114d1487@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=dan.j.williams@intel.com \
--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 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 NNTP newsgroup(s).