From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [StGIT PATCH] Implement a new patch identification scheme and id command
Date: Mon, 16 Jun 2008 16:08:57 +0200 [thread overview]
Message-ID: <20080616140857.GA24433@diana.vm.bytemark.co.uk> (raw)
In-Reply-To: <b0943d9e0806160630m12f5bc7x39053e6c81d983c0@mail.gmail.com>
On 2008-06-16 14:30:32 +0100, Catalin Marinas wrote:
> What about supporting patch ranges with the new id format, something
> like:
>
> branch:patch1..patch2,patch3
>
> or
>
> branch:patch1..patch2 branch:patch3
Yes, that's a good idea; the endpoints of a range have to be on the
same branch no matter what, so having the branch: prefix apply to both
of the endpoint patches in "branch:patch1..patch2" is a good idea.
I'm not sure if the comma notation is worth it. And if it turns out to
have been useful, we can just advise users to write
$ stg foo branch:{p1..p2,p3}
which the shell will expand to
$ stg foo branch:p1..p2 branch:p3
> This way we could get rid of many --branch options.
Indeed.
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle
prev parent reply other threads:[~2008-06-16 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 7:28 [StGIT PATCH] Implement a new patch identification scheme and id command Catalin Marinas
2008-06-14 7:32 ` Catalin Marinas
2008-06-14 9:47 ` Karl Hasselström
2008-06-16 10:00 ` Catalin Marinas
2008-06-16 13:30 ` Catalin Marinas
2008-06-16 14:08 ` Karl Hasselström [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080616140857.GA24433@diana.vm.bytemark.co.uk \
--to=kha@treskal.com \
--cc=catalin.marinas@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).