Re: [PATCH 1/2] Introduce git-run-with-user-path helper program.

From: Petr Baudis <pasky@ucw.cz>
Date: May 18, 2005, 23:24 UTC
Message-ID: <20050518232408.GA18281@pasky.ji.cz>
In-Reply-To: <7vekc4nom5.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Thu, May 19, 2005 at 12:41:38AM CEST, I got a letter where Junio C Hamano <junkio@cox.net> told me that...

Show 17 quoted lines

> >>>>> "PB" == Petr Baudis <pasky@ucw.cz> writes:
> 
> >> $ pwd
> >> /usr/src/linux/fs
> >> $ git-run-with-user-path cg-commit -- ext?/Makefile
> >> 
> >> would work.
> 
> PB> Yes. But if you do just cg-commit in the subdirectory, it won't work.
> 
> The point of git-run-with-user-path is that it canonicalizes and
> filters the paths, chdir(2)'s to GIT_PROJECT_TOP before running
> cg-commit.  So when cg-commit starts in the above example,
> 
>     (1) its $cwd is /usr/src/linux and your .git subdirectory is
>         right there in ./.git/
>     (2) it gets fs/ext2/Makefile and fs/ext3/Makefile as arguments.

Yes. My point is that sometimes the Cogito commands have directory-specific functionality even when called without any arguments.

$ pwd /usr/src/linux $ date >>README $ cd fs $ date >>Makefile $ cg-commit

will commit only the fs/Makefile change.

Show 7 quoted lines

> >> BTW, I am wondering if your choice of cg-commit as an example
> >> (as opposed to something else like diff or add) is a flamebait
> >> or just an innocent random example ;-)?
> 
> PB> It was completely innocent. :-) How would it be a flamebait?
> 
> <http://members.cox.net/junkio/per-file-commit.txt> ;-).

JIT's snapshotting makes up for it, I think. It has some beauty. :-)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor