From: Kirill Smelkov <kirr@landau.phys.spbu.ru>
To: martin f krafft <madduck@madduck.net>
Cc: Petr Baudis <pasky@suse.cz>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH (topgit)] tg-patch: add support for generating patches against worktree and index
Date: Thu, 8 Jan 2009 23:16:15 +0300 [thread overview]
Message-ID: <20090108201614.GA4185@roro3> (raw)
In-Reply-To: <20090108195356.GA14644@lapse.rw.madduck.net>
On Fri, Jan 09, 2009 at 08:53:56AM +1300, martin f krafft wrote:
> also sprach Kirill Smelkov <kirr@landau.phys.spbu.ru> [2009.01.09.0722 +1300]:
> > This implements `tg patch -i` and `tg patch -w` to see current
> > patch as generated against not-yet-committed index and worktree.
>
> I think at this early stage, it would make sense to use long options
> and not reserve short options yet. Unless Petr disagrees, I'd kindly
> ask you to use long options instead. Once TopGit has been around for
> a while, we can provide short options for the most important long
> options.
>
> This is possibly too conservative, but I've been bitten by lack of
> new letters before because I've used them all up for options that
> later turned out not to be needed.
I agree, but when I found myself needing something like
`tg patch --index`, I've spot this in README:
--- a/README
+++ b/README
@@ -284,8 +284,9 @@ tg patch
tg patch will be able to automatically send the patches by mail
or save them to files. (TODO)
- TODO: tg patch -i to base at index instead of branch,
- -w for working tree
So I concluded -i/-w was planned from the beginning.
I myself would call these options --index and --work or something
like that, but I'll be ok with any option.
Thanks,
Kirill
next prev parent reply other threads:[~2009-01-08 20:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 18:22 [PATCH (topgit)] tg-patch: add support for generating patches against worktree and index Kirill Smelkov
2009-01-08 19:53 ` martin f krafft
2009-01-08 20:16 ` Kirill Smelkov [this message]
2009-01-08 21:11 ` Kirill Smelkov
2009-01-18 15:06 ` Kirill Smelkov
2009-01-20 0:21 ` martin f krafft
2009-01-20 17:56 ` Kirill Smelkov
2009-01-21 3:20 ` martin f krafft
2009-01-21 20:26 ` Kirill Smelkov
2009-01-22 0:28 ` martin f krafft
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=20090108201614.GA4185@roro3 \
--to=kirr@landau.phys.spbu.ru \
--cc=git@vger.kernel.org \
--cc=madduck@madduck.net \
--cc=pasky@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.