From: "David Kågedal" <davidk@lysator.liu.se>
To: git@vger.kernel.org
Subject: Re: [RFC PATCH] Rename "bury" back to "sink".
Date: Sun, 13 May 2007 11:28:23 -0700 [thread overview]
Message-ID: <87zm48wpbs.fsf@morpheus.local> (raw)
In-Reply-To: 20070505201307.GE19253@nan92-1-81-57-214-146.fbx.proxad.net
Yann Dirson <ydirson@altern.org> writes:
> Side note about the "stg move" name: yes it could possible to mistake it
> for "move file" (especially as we don't have "stg mv"). My current
> state of mind would be to drop add/rm/cp from stgit, and move the "stg
> cp" logic to a new git-cp command. This way, stgit would just be
> about handling series of patches, with git being used for the
> working-copy. Any opinions on this ?
For this reason, and others, I think "stg reorder" would be better.
Especially if you implement Karl's suggestion of reordering all
patches in an editor.
--
David Kågedal
next prev parent reply other threads:[~2007-05-13 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 22:53 [RFC PATCH] Rename "bury" back to "sink" Yann Dirson
2007-05-04 23:22 ` Jakub Narebski
2007-05-05 20:13 ` Yann Dirson
2007-05-06 10:49 ` Karl Hasselström
2007-05-13 18:28 ` David Kågedal [this message]
2007-05-13 19:06 ` Karl Hasselström
2007-05-05 13:13 ` Karl Hasselström
2007-05-05 17:35 ` Chris Shoemaker
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=87zm48wpbs.fsf@morpheus.local \
--to=davidk@lysator.liu.se \
--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