git-blame-prefix-format
- %h %20A:
+ %h %20.20A:
The format of the prefix added to each line in `git-blame'
mode. The format is passed to `format-spec' with the following format keys:
--
David Kågedal
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message
($date)),
git-commit-tree, $tree,@par);
die Cannot exec git-commit-tree: $!\n;
--
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
...
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
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 user, you never see the -script ending anyway. You'd never
type
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
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo
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 that this patch was accepted, which
?
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 from this list: send the line unsubscribe git in
the body of a message to [EMAIL
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
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: send the line unsubscribe git in
the body of a message
.
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 insertions(+), 3 deletions
.
--
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
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 as I can till, this F probably came from the CVS
12 matches
Mail list logo
