git-cvs-import-script problems

pointing to refs/heads/origin. -- David Kågedal - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: git-cvs-import-script problems

David Kågedal <[EMAIL PROTECTED]> writes: > I just tried importing a large CVS repository to git, using "git > cvsimport". It managed to import a lot of files and revisions, but > half-way through, it stopped with this message: > > Unknown: F > > As far

[PATCH] Fixed two bugs in git-cvsimport-script.

h they were not handled. I also updated the documentation for that script to correspond to actual flags. Signed-off-by: David Kågedal <[EMAIL PROTECTED]> --- Documentation/git-cvsimport-script.txt |9 - git-cvsimport-script |4 ++-- 2 files changed, 10 inser

Re: Importing from CVS issues

s/heads/origin': No such > file or directory Was this done with an empty destination dir? I've seen similar things happen in a dir where an interrupted cvs import was done previously, and the 'origin' branch was never created. -- David Kågedal - To unsubscribe from this list: s

Re: [PATCH] Fixed two bugs in git-cvsimport-script.

David Kågedal <[EMAIL PROTECTED]> writes: > The git-cvsimport-script had a copule of small bugs that prevented me > from importing a big CVS repository. > > The first was that it didn't handle removed files with a multi-digit > primary revision number. I noticed th

Re: [PATCH] Fixed two bugs in git-cvsimport-script.

is the character encoding for commit objects in your git repository? It is obviously one that is compatible with ASCII, which probably leaves you with the alternatives ASCII, Latin1, and UTF-8. And plain ASCII obviously doesn't work very well for me. -- David Kågedal - To unsubscribe fro

Re: [PATCH] Fixed two bugs in git-cvsimport-script.

t;issue (so is blob contents encoding). Agreed. And your response is probably good enough for now. I also think that having UTF-8 as the standard convention is the way to go. -- David Kågedal - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Teach applymbox to keep the Subject: line.

ontent encodings? We probably need to separate the two. Note that I'm not really talking about your patch handling for Linux; you are free to disallow my name in Linux patches if you want to. But I'd like to see a way to get rid of that limitation for other uses of git. -- David Kågedal

Re: Tool renames? was Re: First stab at glossary

ce with "-script" suffixes. Calling the command git-foobar makes much more sense, and allows us to reimplement the scripts as binaries, or whatever. So your argument that it makes it easier for git developers to work with the source doesn't help the user. The consequence is maybe that th

Re: Tool renames? was Re: First stab at glossary

Linus Torvalds <[EMAIL PROTECTED]> writes: > On Mon, 5 Sep 2005, David Kågedal wrote: >> >> But to the users (like myself), there's no point in naming it by >> whether it's a script or a binary. > > So? There's no downside. > > To you, as a

Re: Tool renames? was Re: First stab at glossary

t read-cache' should work too. And 'git ls-files', and 'git rev-parse', and 'git merge-one-file' and 'git sh-setup-script' in decreasing order of usefulness... But running 'git' without arguments only list the -script commands as available. -- David Kågedal - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

[PATCH] Added an option to cvsimport to specify email domain

The authorship info in commits created by git-cvsimport-script only contains the username of the CVS committer. This patch adds a flag -e to git-cvsimport-script that makes it possible to specify an email domain that is added to all email addresses in the commit "author" and "committer" fields.

Re: [PATCH/RFC] git-blame.el: truncate author to avoid jagged left edge of code

f --git a/contrib/emacs/git-blame.el b/contrib/emacs/git-blame.el >index d351cfb6..137d5ba9 100644 >--- a/contrib/emacs/git-blame.el >+++ b/contrib/emacs/git-blame.el >@@ -102,7 +102,7 @@ > :group 'git-blame) > > (defcustom git-blame-prefix-format >- "%h %20A:"