From: martin@catalyst.net.nz
To: git@vger.kernel.org
Cc: Martin Langhoff <martin@catalyst.net.nz>
Subject: [PATCH 3/5] archimport - update in-script doco, options tidyup
Date: Sun, 11 Sep 2005 21:26:05 +1200 [thread overview]
Message-ID: <11264307653007-git-send-email-martin@catalyst.net.nz> (raw)
In-Reply-To: <1126430765435-git-send-email-martin@catalyst.net.nz>
Updated the usage/help message to match asciidoc documentation. The perldoc
documentation now includes the first paragraph from the asciidoc documentation
and points users to the manpage.
Updated TODO section.
Removed some redundant options from the getopt() invocation.
Signed-off-by: Martin Langhoff <martin@catalyst.net.nz>
---
git-archimport.perl | 33 ++++++++++++++++-----------------
1 files changed, 16 insertions(+), 17 deletions(-)
8d625fb42f58a6b4b2af135efe76726e8f0579e0
diff --git a/git-archimport.perl b/git-archimport.perl
--- a/git-archimport.perl
+++ b/git-archimport.perl
@@ -6,23 +6,27 @@
# The basic idea is to walk the output of tla abrowse,
# fetch the changesets and apply them.
#
+
=head1 Invocation
- git-archimport -i <archive>/<branch> [<archive>/<branch>]
- [ <archive>/<branch> ]
+ git-archimport [ -h ] [ -v ] [ -T ] [ -t tempdir ] <archive>/<branch> [ <archive>/<branch> ]
- The script expects you to provide the key roots where it can start the
- import from an 'initial import' or 'tag' type of Arch commit. It will
- then follow all the branching and tagging within the provided roots.
+Imports a project from one or more Arch repositories. It will follow branches
+and repositories within the namespaces defined by the <archive/branch>
+parameters suppplied. If it cannot find the remote branch a merge comes from
+it will just import it as a regular commit. If it can find it, it will mark it
+as a merge whenever possible.
- It will die if it sees branches that have different roots.
+See man (1) git-archimport for more details.
-=head2 TODO
+=head1 TODO
- - keep track of merged patches, and mark a git merge when it happens
- - smarter rules to parse the archive history "up" and "down"
- - be able to continue an import where we left off
+ - create tag objects instead of ref tags
- audit shell-escaping of filenames
+ - better handling of temp directories
+ - use GIT_DIR instead of hardcoded ".git"
+ - hide our private tags somewhere smarter
+ - find a way to make "cat *patches | patch" safe even when patchfiles are missing newlines
=head1 Devel tricks
@@ -54,14 +58,13 @@ our($opt_h,$opt_v, $opt_T,
sub usage() {
print STDERR <<END;
Usage: ${\basename $0} # fetch/update GIT from Arch
- [ -h ] [ -v ] [ -T ]
- [ -C GIT_repository ] [ -t tempdir ]
+ [ -h ] [ -v ] [ -T ] [ -t tempdir ]
repository/arch-branch [ repository/arch-branch] ...
END
exit(1);
}
-getopts("ThviC:t:") or usage();
+getopts("Thvt:") or usage();
usage if $opt_h;
@ARGV >= 1 or usage();
@@ -71,10 +74,6 @@ my $tmp = $opt_t;
$tmp ||= '/tmp';
$tmp .= '/git-archimport/';
-my $git_tree = $opt_C;
-$git_tree ||= ".";
-
-
my @psets = (); # the collection
my %psets = (); # the collection, by name
next prev parent reply other threads:[~2005-09-11 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 9:26 archimport documentation updates and tidyups martin
2005-09-11 9:26 ` [PATCH 1/5] archimport documentation update martin
2005-09-11 9:26 ` [PATCH 2/5] archimport documentation tidyup martin
2005-09-11 9:26 ` martin [this message]
2005-09-11 9:26 ` [PATCH 4/5] archimport - use GIT_DIR instead of hardcoded ".git" martin
2005-09-11 9:26 ` [PATCH 5/5] archimport - better handling of temp dirs martin
2005-09-11 14:58 ` [PATCH 1/5] archimport documentation update A Large Angry SCM
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=11264307653007-git-send-email-martin@catalyst.net.nz \
--to=martin@catalyst.net.nz \
--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).