From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Yann Dirson" <ydirson@altern.org>
Cc: "GIT list" <git@vger.kernel.org>
Subject: Re: "stgit clean" has problems with removed generated files
Date: Wed, 6 Dec 2006 13:12:53 +0000 [thread overview]
Message-ID: <b0943d9e0612060512w272d656dwa3ef5b6875abf8fa@mail.gmail.com> (raw)
In-Reply-To: <20061123192831.GL5443@nan92-1-81-57-214-146.fbx.proxad.net>
On 23/11/06, Yann Dirson <ydirson@altern.org> wrote:
> On Thu, Nov 23, 2006 at 04:33:42PM +0000, Catalin Marinas wrote:
> > >First, when cleaning patches, we could first look up which patches are
> > >to be removed, and only pop the necessary ones.
I fixed this.
> > Is there any other place where ranges could be used but aren't?
>
> Hm, let's see... I'd say "export" (I have missed it already), "files"
> and maybe "commit" and "pick", although the latter would require a syntax
> for ranges in other branch.
I changed the export command to take a range of patches as arguments
(and a --dir option for the export directory).
> While reviewing the various commands for this, I realized that "stg pop
> <patch>" semantics is significantly different from "stg push <patch>" -
> ie. it is an equivalent of "goto". What about turning it into a
> float+pop, to better match the "push" behaviour ?
Thanks for the suggestion, I fixed pop to take patch ranges now.
> I also realized that "stg help <command>" output does not go through to
> the pager, while eg. the help for "mail" is quite long.
Added this feature as well. I'll try to push the changes tonight.
--
prev parent reply other threads:[~2006-12-06 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 16:11 "stgit clean" has problems with removed generated files Yann Dirson
2006-11-23 16:33 ` Catalin Marinas
2006-11-23 19:28 ` Yann Dirson
2006-11-24 8:20 ` Jakub Narebski
2006-12-06 13:12 ` 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=b0943d9e0612060512w272d656dwa3ef5b6875abf8fa@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=ydirson@altern.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).