Re: user-manual: patch proposals and questions

2018-03-23 Thread kalle
thank you for your answer and hints. kalle Am 19.03.2018 um 01:27 schrieb Eric Sunshine: > On Sun, Mar 18, 2018 at 7:49 PM, kalle wrote: >> 1.I wonder, why the "user-manual" is so hidden on the (official?) site >> git-scm.com [it is accessible at git-scm.com/docs/u

Fwd: user-manual: patch proposals and questions

2018-03-18 Thread kalle
the 'user-manual' 3.it would be for non-graphics-users to have the Git-Pro-book in text-format. thanks, kalle Weitergeleitete Nachricht Betreff: user-manual: patch proposals and questions Datum: Tue, 6 Mar 2018 00:08:55 +0100 Von: kalle An: git@vger.kernel.org The

Re: git help clone: questions

2018-03-07 Thread kalle
Am 07.03.2018 um 23:45 schrieb Junio C Hamano: > kalle writes: > >> Am 06.03.2018 um 02:36 schrieb Junio C Hamano: >>> kalle writes: >>> >>>> -In the explanation of the option --reference: shouldn't there be >>>> written '

Re: git help clone: questions

2018-03-07 Thread kalle
I wrote this, because when it is written about 'reference repository', I consider it not totally clear, which repository is meant, as the option '--reference ' only names one as . For reasons of clearness, I now propose writing "reference repository ". kalle Am 06.

Re: man gittutorial: patch proposal

2018-03-07 Thread kalle
ing concept. But it could also be me... 2.yes please. I will read this section. kalle Am 06.03.2018 um 00:25 schrieb Jonathan Nieder: > Hi, > > kalle wrote: > >> see attachment. > > Thanks for writing. A few questions: > > 1. Can you say a little more about t

user-manual: patch proposals and questions

2018-03-05 Thread kalle
uot;Check whether two branches point at the same history": 'git diff origin..master' -> shouldn't it be rather 'git diff branch1..branch2'? … or rewrite the example with branch1=origin and branch2=master. greetings, kalle >From 19061a0dd4363edbf8757a5e9eee8ace210f4029

user-manual: patch proposals and questions

2018-03-05 Thread kalle
uot;Check whether two branches point at the same history": 'git diff origin..master' -> shouldn't it be rather 'git diff branch1..branch2'? … or rewrite the example with branch1=origin and branch2=master. greetings, kalle

git help clone: questions

2018-03-05 Thread kalle
-In the explanation of the option --reference: shouldn't there be written '' instead of 'reference repository'? greetings, kalle

man gittutorial: patch proposal

2018-03-05 Thread kalle
see attachment. greetings, kalle >From ed466d29733a14acf3b2071d3d35aa829e09b1d7 Mon Sep 17 00:00:00 2001 From: kalledaballe Date: Thu, 8 Feb 2018 18:53:54 +0100 Subject: [PATCH 1/5] I corrected some few quotation mistakes --- Documentation/gittutorial.txt | 6 +++--- 1 file changed

Re: What's cooking in git.git (Nov 2012, #02; Fri, 9)

2012-11-10 Thread Kalle Olavi Niemitalo
Paul Fox writes: > you're sending SIGINT to the cvs commit command, and that causes the > editor to die right away? That's right. It is not a quirk of shell-mode in Emacs, because I get the same result with ^C in xterm too. % EDITOR="$HOME/prefix/x86_64-unknown-linux-gnu/bin/emacsclient --curr

Re: What's cooking in git.git (Nov 2012, #02; Fri, 9)

2012-11-10 Thread Kalle Olavi Niemitalo
Paul Fox writes: > when i implemented the change, i wondered if some twisted emacs > workflow would be an issue. ;-) and i almost blocked SIGQUIT as > well -- the two programs i looked at for precedent (CVS and MH) both > block both SIGQUIT and SIGINT when spawning an editor. > > but since emacs

Re: What's cooking in git.git (Nov 2012, #02; Fri, 9)

2012-11-09 Thread Kalle Olavi Niemitalo
Jeff King writes: > Comments welcome from people using unusual editors (e.g., a script that > starts an editor in another window then blocks, waiting for the user to > finish). I often run a shell in Emacs in X, then start git commit in that shell. $EDITOR is emacsclient --current-frame, whi

Re: git with large files...

2012-07-23 Thread Kalle Launiala
2012/7/23 Sitaram Chamarty : > On Mon, Jul 23, 2012 at 2:24 AM, Junio C Hamano wrote: >> mer...@stonehenge.com (Randal L. Schwartz) writes: >> "Darek" == Darek Bridges writes: >>> >>> Darek> I use git for many things, but I am trying to work out the >>> Darek> workflow to use git for dep

Re: git with large files...

2012-07-22 Thread Kalle Launiala
eal problem with big files performance or storage files? Anything else than "uncommon" slowness on calculating and comparing large file sha1 hashes? Kalle -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Complete audit trail for embedded (Linux) system lifecycle with Git

2012-07-15 Thread Kalle Launiala
form XML-database for metadata indexing - grid databases being considered for the larger implementations. Any comments and/or feedback would be greatly appreciated. Cheers, Kalle Launiala -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to major

Re: Could not interpret heads/dbrt-test as something to pull

2005-09-04 Thread Kalle Valo
Junio C Hamano <[EMAIL PROTECTED]> writes: >> Rsync works for me also. But HTTP is still broken. > > Sorry, a broken repo. Fix made on master should percolate > through soonish. HTTP clone works now, thanks. -- Kalle Valo - To unsubscribe from this list: send the line

Re: Could not interpret heads/dbrt-test as something to pull

2005-09-04 Thread Kalle Valo
gh. Rsync works for me also. But HTTP is still broken. -- Kalle Valo - 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

Could not interpret heads/dbrt-test as something to pull

2005-09-04 Thread Kalle Valo
I'm using git compiled earlier this week on Debian unstable. -- Kalle Valo - 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: cvsimport error: need a valid pathname

2005-08-27 Thread Kalle Valo
Martin Langhoff <[EMAIL PROTECTED]> writes: > On 8/28/05, Kalle Valo <[EMAIL PROTECTED]> wrote: >> The documentation says that it should be possible to update >> incrementally from the CVS repository. Am I doing something wrong or >> is this a bug? > > It _

Re: [RFC] undo and redo

2005-08-25 Thread Kalle Valo
just a backup if (read: when) I undo something important, nothing more. For anything else I would use branches, as was suggested. -- Kalle Valo - 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] Change git-branch to list branches

2005-08-17 Thread Kalle Valo
Kalle Valo <[EMAIL PROTECTED]> writes: > Junio C Hamano <[EMAIL PROTECTED]> writes: > >> I do not think we have agreed to limit ourselves to a flat >> namespace under refs/heads without subdirectories. Something >> like what git-show-branches-script does

Re: [PATCH] Change git-branch to list branches

2005-08-17 Thread Kalle Valo
send a revised patch soon. -- Kalle Valo - 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] Change git-branch to list branches

2005-08-16 Thread Kalle Valo
If no argument provided to `git branch`, show available branches and mark current branch with star. This is based on patch written by Amos Waterland <[EMAIL PROTECTED]>. Signed-off-by: Kalle Valo <[EMAIL PROTECTED]> --- git-branch-script |8 +++- 1 files changed, 7 inse

Re: [PATCH] Add git-branches-script

2005-08-16 Thread Kalle Valo
x27;git branch' command and 'git branches' is too similar. I think they should be merged. I have a patch coming up. -- Kalle Valo - 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] Fix debian doc-base

2005-08-03 Thread Kalle Valo
Fixed location of HTML documents in debian doc-base file. Without this fix debian package won't install properly (complains about missing /usr/share/doc/git-core/html directory). --- debian/git-core.doc-base |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) 194759c0447f88804dfb43615