From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-format-patch possible regressions
Date: Fri, 26 May 2006 08:26:49 +0200 [thread overview]
Message-ID: <e56734$nj7$1@sea.gmane.org> (raw)
In-Reply-To: 7v4pzdqpit.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> So the way for qgit to use it would become something like this.
> Instead of giving a list of ranges like "a..b c..d e..f":
>
> * Run "format-patch a..b"; by reading from its stdout you know
> what patches you got -- you count them.
>
> * Run "format-patch --start-number=6 c..d" (if you got 5 out of
> a..b);
[...]
I still think that having _shortcut notation_ being different for very
different commands is not a bad idea.
If one is really concerned about consistency of rev-list options, we could
use ',' or something to separate separate lists of commits, e.g.
git format-patch a..b , c..d , e..f
or
git format-patch a..b --then c..d --then e..f
What do you think about the idea?
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-05-26 6:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 19:23 git-format-patch possible regressions Marco Costalba
2006-05-25 19:43 ` Linus Torvalds
2006-05-25 20:10 ` Marco Costalba
2006-05-25 19:56 ` Junio C Hamano
2006-05-25 20:21 ` Marco Costalba
2006-05-25 21:55 ` Johannes Schindelin
2006-05-25 22:18 ` Johannes Schindelin
2006-05-25 23:11 ` Junio C Hamano
2006-05-25 23:28 ` Johannes Schindelin
2006-05-26 6:09 ` Marco Costalba
2006-05-26 6:16 ` Junio C Hamano
2006-05-26 6:26 ` Jakub Narebski [this message]
2006-05-27 9:12 ` Marco Costalba
2006-05-28 9:57 ` Johannes Schindelin
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='e56734$nj7$1@sea.gmane.org' \
--to=jnareb@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.
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).