From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [StGit PATCH 2/6] Remove TODO items that have already been addressed
Date: Sun, 05 Oct 2008 18:01:40 +0200 [thread overview]
Message-ID: <20081005160140.19886.92390.stgit@yoghurt> (raw)
In-Reply-To: <20081005155450.19886.43748.stgit@yoghurt>
Signed-off-by: Karl Hasselström <kha@treskal.com>
---
TODO | 9 ---------
1 files changed, 0 insertions(+), 9 deletions(-)
diff --git a/TODO b/TODO
index ff52a95..3570345 100644
--- a/TODO
+++ b/TODO
@@ -1,14 +1,9 @@
The TODO list before 1.0:
- more regression tests
-- stg help should probably pipe through the $PAGER
-- fix StGIT to run correctly in subdirectories
- use a separate index for some commands (refresh, fold etc.) so that
files already added/removed are not automatically checked in
-- debian package support
-- man page
- document the workflow on the StGIT wiki
-- use same configuration file as GIT
- release 1.0
@@ -18,9 +13,5 @@ The future, when time allows or if someone else does them:
- multiple heads in a patch - useful for forking a patch,
synchronising with other patches (diff format or in other
repositories)
-- commit directly to a patch which is not top
-- patch synchronisation between between branches (as some people,
- including me have the same patches based on different branches and
- they have scripts for moving the changes in one to the others)
- numeric shortcuts for naming patches near top (eg. +1, -2)
- (config?) parameter for number of patches included by "series -s"
next prev parent reply other threads:[~2008-10-05 16:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 16:01 [StGit PATCH 0/6] Documentation updates Karl Hasselström
2008-10-05 16:01 ` [StGit PATCH 1/6] Remove unused variable Karl Hasselström
2008-10-05 16:01 ` Karl Hasselström [this message]
2008-10-06 20:43 ` [StGit PATCH 2/6] Remove TODO items that have already been addressed Catalin Marinas
2008-10-07 7:05 ` Karl Hasselström
2008-10-05 16:01 ` [StGit PATCH 3/6] We're half-way there with the separate indexes Karl Hasselström
2008-10-05 16:01 ` [StGit PATCH 4/6] Add 1.0 TODO items from recent discussion by private mail Karl Hasselström
2008-10-06 20:50 ` Catalin Marinas
2008-10-07 7:07 ` Karl Hasselström
2008-10-05 16:01 ` [StGit PATCH 5/6] Refresh the main stg man page Karl Hasselström
2008-10-06 21:14 ` Catalin Marinas
2008-10-06 21:30 ` Samuel Tardieu
2008-10-07 7:40 ` Karl Hasselström
2008-10-06 21:15 ` Catalin Marinas
2008-10-07 7:32 ` Karl Hasselström
2008-10-05 16:02 ` [StGit PATCH 6/6] Refresh and expand the tutorial (not finished) Karl Hasselström
2008-10-06 21:25 ` Catalin Marinas
2008-10-07 7:12 ` Karl Hasselström
2008-10-08 9:24 ` Karl Hasselström
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=20081005160140.19886.92390.stgit@yoghurt \
--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.
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).